Controlling Distribution of Resources on a Network

ABSTRACT

Disclosed are various embodiments for controlling distribution of resources on a network. In one embodiment, a distribution service receives a request from a client device to access resources hosted by a distribution service. In response, the distribution service determines whether the client device is authorized to access the distribution service. The distribution service identifies which of the resources hosted by the distribution service are accessible to the client device based on the resource grouping identifiers associated with the client device. The distribution service determines which distribution rules are associated with the identified resources, the distribution rules including location rules and time rules. The distribution service then transmits the identified resources and identified distribution rules to the client device, where the resources are configured to be exclusively accessible via a containerized client application on the client device while the client device satisfies the distribution rules associated with the resources.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation-in-part of application Ser. No.13/396,356, filed on Feb. 14, 2012. The patent application identifiedabove is incorporated herein by reference in its entirety.

BACKGROUND

Controlling access to and distribution of enterprise resources, such asdocuments, databases, and executable applications, in a networkedenvironment is critical to ensure that only authorized users andnetwork-connected devices may gain access to sensitive information.Depending on the sensitivity of a given resource, an array ofauthorization rules may be necessary to ensure that the resource isadequately protected. Some resources may only require ensuring that theproper user is requesting the resource. Other resources may requirecompliance with more stringent authorization rules, such as determiningwhether the client device is located within an authorized location,determining whether the current time is within an authorized timewindow, determining whether an appropriate transport protocol is used(i.e., http and/or https) by the requesting device, determining whetherthe resource is accessed from a secured device, etc.

To date, enterprises have distributed resources to network-connectedresources using internal secured networks and VPN tunnels to thosenetworks. While these methods provide a secure channel for distribution,these methods typically do not authenticate the recipient beyondensuring a proper recipient. Additionally, these methods are ineffectiveto continuously ensure that the resource is protected, as they fail toensure that the resource is protected beyond the initial grant of accessto the resource. This is problematic because the recipient of theresource may at some point cease to comply with the conditions requiredto receive access to the resource. Consequently, these methods fails tocontinuously ensure that only authorized client devices retain access tolocation-sensitive and time-sensitive resources. Finally, these methodsdo not restrict an authorized recipient from subsequently transmittingcertain resources to other potentially unauthorized recipients.

SUMMARY OF THE INVENTION

Disclosed are embodiments for a non-transitory computer-readable mediumembodying a program executable in a computing device, the programcomprising code that, when executed by a computing device, causes thecomputing device to perform a method comprising the steps of receiving aclient device request to access resources hosted by a distributionservice, determining whether the client device is authorized to accessthe distribution service, identifying the resource grouping identifiersassociated with client devices authorized to access the distributionservice, identifying the resources associated with the identifiedresource grouping identifiers, identifying the distribution rulesassociated with the identified resources including location rules andtime rules, transmitting the identified resources and identifieddistribution rules to the client device, the resources being configuredto be exclusively accessible via a containerized client side applicationon the client device while the client device satisfies the distributionrules.

Disclosed are embodiments for a containerized application executed by aclient device for determining whether the client device is located at anauthorized location, transmitting a request for access to resourceshosted by a distribution service if the client device is located at anauthorized location, receiving resources that are configured to beexclusively accessible via the containerized client side application,and removing the resources from the client device if the client deviceis no longer at an authorized location.

Disclosed are embodiments for a computing device configured to execute adistribution service for controlling distribution of resources in anetworked environment. The distribution service comprises a processorand a memory device including instructions that when executed by theprocessor cause the processor to perform a method comprising the stepsof receiving a client device request to access resources hosted by adistribution service, determining whether the current time associatedwith the client device is within an authorized time window, transmittingthe resources to the client device if the current time associated withthe client device is within an authorized time window, monitoring thecurrent time of the client device on a continuous basis, and removingthe resources from the client device if the current time associated withthe client device is no longer within an authorized time window.

Disclosed are embodiments for a method for receiving a request to accessresources hosted by a distribution service from a client device locatedat an authorized location, transmitting the resources to the clientdevice where the resources are configured to be exclusively accessiblevia a containerized client side application executed on the clientdevice, monitoring the location of the client device on a continuousbasis, and removing the resources from the client device if the clientdevice is no longer at an authorized location.

Disclosed are embodiments for a non-transitory computer-readable mediumembodying a program executable in a computing device, the programcomprising code that, when executed by a computing device, causes thecomputing device to perform a method comprising the steps oftransmitting requests to access resources hosted by a distributionservice from a containerized client side application executed on aclient device and receiving access to the resources if the client deviceis located at an authorized location and if the current time associatedwith the client device is within an authorized time window.

Disclosed are embodiments for a computing device configured to execute adistribution service for controlling distribution of resources in anetworked environment. The distribution service comprises a processorand a memory device including instructions that when executed by theprocessor cause the processor to perform a method comprising the stepsof determining whether a client device has access to resourcesassociated with authorized time windows, determining whether the currenttime associated with the client device is within an authorized timewindow, and removing access to the resources on the client device if thecurrent time associated with the client device is not within anauthorized time window.

BRIEF DESCRIPTION OF THE DRAWINGS

Many aspects of the present disclosure can be better understood withreference to the following diagrams. The drawings are not necessarily toscale, emphasis instead being placed upon clearly illustrating certainfeatures of the disclosure. Moreover, in the drawings, like referencenumerals designate corresponding parts throughout the several views.

FIG. 1 is a block diagram of a networked environment according tocertain exemplary embodiments of the present disclosure.

FIGS. 2-7 are exemplary user interfaces rendered on a client device inthe networked environment of FIG. 1 according to certain embodiments ofthe present disclosure.

FIG. 8 is a flowchart illustrating exemplary functionality performed bya distribution service executed by a distribution server in thenetworked environment of FIG. 1 according to certain embodiments of thepresent disclosure.

FIG. 9 is a flowchart illustrating exemplary functionality performed bya client side application executed by a client device in the networkedenvironment of FIG. 1 according to certain embodiments of the presentdisclosure.

FIG. 10 is a flowchart illustrating exemplary functionality performed bya client side application executed by a client device in the networkedenvironment of FIG. 1 according to certain embodiments of the presentdisclosure.

FIGS. 11-13 are exemplary user interfaces rendered on a client device inthe networked environment of FIG. 1 according to certain embodiments ofthe present disclosure.

FIG. 14 is a flowchart illustrating exemplary functionality performed bya distribution service executed by a distribution server in thenetworked environment of FIG. 1 according to certain embodiments of thepresent disclosure.

FIG. 15 is a flowchart illustrating exemplary functionality performed bya distribution service executed by a distribution server in thenetworked environment of FIG. 1 according to certain embodiments of thepresent disclosure.

FIG. 16 is a flowchart illustrating exemplary functionality performed bya client side application executed by a client device in the networkedenvironment of FIG. 1 according to certain embodiments of the presentdisclosure.

FIG. 17 is a flowchart illustrating exemplary functionality performed bya client side application executed by a client device in the networkedenvironment of FIG. 1 according to certain embodiments of the presentdisclosure.

FIG. 18 shows schematic block diagrams illustrating a distributionserver and client device employed in the networked environment of FIG. 1according to certain embodiments of the present disclosure.

DETAILED DESCRIPTION

Disclosed are various embodiments for systems and methods forcontrolling distribution of resources in a network. The exemplary systemcomprises a distribution server and a plurality of client devicesconfigured as described herein.

In one embodiment, a distribution service executed by a distributionserver transmits resources to a client device if a pairing of a user ofthe client device and the client device are authorized to receive theresources. The distribution service first determines whether the userand client device pairing are authorized to communicate with thedistribution service based at least in part on a plurality ofauthorization rules. For example, an authorization approach as describedin application Ser. No. 13/316,073 entitled “CONTROLLING ACCESS TORESOURCES ON A NETWORK,” which is incorporated herein by reference inits entirety, may be employed to determine whether the client device andthe user of the client device are authorized.

Upon determining that the user and the client device pairing areauthorized, the distribution service determines which of a plurality ofresource grouping identifiers are associated with the user and clientdevice pairing. For instance, each resource may be associated with oneor more resource grouping identifiers. Resource grouping identifiers areused to identify a grouping (i.e., one or more) of resources that may beprovided to authorized user and client device pairings. The distributionservice then identifies a plurality of resources that are associatedwith each one of the resource grouping identifiers and transmits theidentified resources to the client device if the client device satisfiesthe distribution rules associated with each one of the identifiedresources. For instance, the distribution service may determine that theclient device complies with the distribution rules based at least inpart on data selected from a device profile of the client device, suchas location information specifying the location of the client deviceand/or time information specifying the current time.

In one embodiment, the resources referenced herein may include anyelectronic data, such as databases, text files, word processor files,spreadsheet files, presentation files, graphic files, audio files,photographic files, video files, applications and application files,and/or the like. More specifically, resources may include: data files,audio files, video files, three-dimensional image files, raster imagefiles, vector image files, page layout files, spreadsheet files,database files, executable files, CAD files, web files, plug-in files,font files, system files, settings files, encoded files, compressedfiles, disk image files, developer files, backup files, and/or any otherfiles.

FIG. 1 illustrates a networked environment 100 according to variousembodiments. The networked environment 100 includes a network 110, aclient device 120, and a distribution server 150. The network 110 may beor include, for example, any type of wireless network such as a wirelesslocal area network (WLAN), a wireless wide area network (WWAN), or anyother type of wireless network now known or later developed.Additionally, the network 110 may be or include the Internet, intranets,extranets, microwave networks, satellite communications, cellularsystems, PCS, infrared communications, global area networks, or othersuitable networks, etc., or any combination of two or more suchnetworks. In one embodiment, the network 110 facilitates transmission ofresources 165 between one or more client devices 120 and a distributionserver 150.

The client device 120 may be a desktop computer, a laptop computer, apersonal digital assistant, a cellular telephone, a set-top box, a musicplayer, a web pad, a tablet computer system, a game console, and/oranother device with like capability. The client device 120 may include awired network connectivity component (not shown in FIG. 1), for example,an Ethernet network adapter, a modem, and/or the like. The client device120 may further include a wireless network connectivity interface (notshown in FIG. 1), for example, a PCI (Peripheral Component Interconnect)card, USB (Universal Serial Bus) interface, PCMCIA (Personal ComputerMemory Card International Association) card, SDIO (Secure DigitalInput-Output) card, NewCard, Cardbus, a modem, a wireless radiotransceiver, and/or the like. The client device 120 is operable tocommunicate via wired connection with the distribution server 150 withthe aid of the wired network connectivity component. The client device120 is further operable to communicate wirelessly with the distributionserver 150 with the aid of the wireless network connectivity component.Additionally, the client device 120 may further comprise a memory forstoring data and applications, a processor for executing applicationsstored in memory, and a local interface such as a bus, as will bedescribed with respect to FIG. 18.

Additionally, the client device 120 may store in a data store 122 adevice profile 123, user credentials 132, a device identifier 135, andother data. In one embodiment, the device profile 123 may representhardware, software, and security attributes that describe the clientdevice 120. For instance, the device profile 123 may represent hardwarespecifications of the client device 120, version and configurationinformation of various software programs and hardware componentsinstalled on the client device 120, transport protocols enabled on theclient device 120, version and usage information of various otherresources stored on the client device 120, and/or any other attributesassociated with the state of the client device 120. The device profile123 may further include characteristics describing the current state ofthe client device 120, such as location information 133 specifying thelocation of the client device 120 and time information 143 specifyingthe current time. Moreover, the device profile 123 may include dataindicating a date of a last virus scan of the client device 120, a dateof a last access by an IT representative, a date of a last access by thedistribution server 150, a date of a last service by the ITrepresentative, and/or any other data indicating a date of lastmaintenance.

The user credentials 132 may uniquely identify the user of the clientdevice 120. For example, the user credentials 132 may include ausername, a password, and/or biometric data related to facialrecognition, retina recognition, fingerprint recognition, and the like.The device identifier 135 may uniquely identify the client device 120.For example, the device identifier 135 may be a unique hardwareidentifier such as a GUID (Globally Unique Identifier), UUID(Universally Unique Identifier), UDID (Unique Device Identifier), serialnumber, IMEI (Internationally Mobile Equipment Identity), Wi-Fi MAC(Media Access Control) address, Bluetooth MAC address, a CPU ID, and/orthe like, or any combination of two or more such hardware identifiers.Additionally, the device identifier 135 may be represented by a uniquesoftware identifier such a token or certificate, based at least in parton the aforementioned unique hardware identifiers.

The client device 120 may further be configured to execute variousapplications. For example, the client device 120 may be configured toexecute applications such as web browsing applications, emailapplications, instant messaging applications, and/or other applicationscapable of receiving and/or rendering resources 165 on a display 136associated with the client device 120. Any applications capable ofreceiving and/or rendering resources 165 on a display 136 is generallyreferred to herein as a “client side application” 126. The client sideapplication 126 may be stored in the memory of the client device 120. Inone embodiment, the client side application 126 may be a securecontainer program that may be authorized to receive and render selectedresources 165, as described herein. The secure container program mayfurther contain a decryption key specific to a distribution service 174that enables the secure container program to decrypt resources 165transmitted by the distribution service 174 that have been encrypted bythe distribution service 174 to prevent unauthorized programs fromaccessing the resources 165 on the client device 120. In anotherembodiment, the client side application 126 may be a browser configuredto be executed as described herein.

The client side application 126 may executed to transmit requests toaccess resources 165 to the distribution server 150 and render a userinterface 137 on the display 136 that provides access to the resources165. In particular, the resources 165 may be presented in a userinterface 137 by decompressing compressed files and presenting theuncompressed files, mounting disk image files and presenting the mountedimage files, running executable files and presenting the executed files,by enabling a data search of the resources 165 and presenting thefeatured output in a user interface, by calling on another applicationon the client device 120 to respond to data links contained within theresources 165, and/or by transmitting a part or the whole of theresources 165 to another application on the client device 120.Furthermore, a client side application 126 may be executed to present asingle resource 165 or a series of resources 165 in a comprehensivemanner, for instance, presenting photograph files in a slideshowpresentation. Additionally, the client side application 126 may beexecuted to render an environment that presents an array of resources165 in a single view, such as a category-based tree or outline format,based at least in part on a resource qualifier 172 associated with theresources 165.

In one embodiment, the resource qualifier 172 may be or include metadatathat describes and/or regulates the use of the respective resource 165.For example, a resource qualifier may include categories/sub-categoriesto which the resource 165 belongs, an indication that the resource 165is considered a favorite, an indication of whether the resource 165 isprivately owned, publicly owned, and/or enterprise-owned, an indicationof whether the resource 165 is confidential, an indication of whetherthe resource 165 is password protected, an indication of the historicalversion of the resource 165, a description of the resource 165, one ormore comments regarding the resource 165, an indication of the size andformat of the resource 165, an indication of the download priorityassociated with the resource 165, an indication of the expiration dateassociated with the resource 165, an indication of the effective dateassociated with the resource 165, an indication of the ownership of theresource 165, an indication of the managing party of the resource 165,and/or the like, or any combination of resource qualifiers 172.Additionally, the resource qualifiers 172 may indicate that theresources 165 are encrypted and may facilitate the decryption of theresources 165 when the client device 120 has access to an appropriatedecryption key, such as a decryption key provided by a distributionservice 174 associated with the resources 165.

The client side application 126 may also facilitate the modification ofresources 165 provided by the distribution service 174 and themodification of data associated with the provided resources 165. Forexample, the client side application 126 may include functionality foradding content to the existing resources 165, removing content from theexisting resources 165, altering the content of existing resources 165,adding resource qualifiers 172 associated with the existing resources165, and/or the like, or any combination of manipulations of theresources 165.

The client side application 126 may further be executed to add newresources 165 to be hosted by the distribution server 150. For example,a user having administrator-level user credentials 132 may manipulatethe user interface 137 to transfer copies of resources 165 locallystored on the client device 120 to the distribution server 150 to beincluded in the data store 153. In one embodiment, the user of theclient device 120 may initiate an upload of one or more resources 165via the user interface 137 rendered by the client side application 126,as can be appreciated. In addition, the user may specify one or moreapproved resource grouping identifiers 168 that are permitted to accessthe uploaded resource 165 and specify distribution rules 171 that arerequired to be complied with in order to access the uploaded resource165, as will be described. In another embodiment, a user withoutadministrator-level user credentials 132 may manipulate the userinterface 137 to transfer local copies of personal resources 165 to thedistribution server 150. In this example, the resources qualifiers 172associated with the personal resources 165 may be configured by defaultto restrict access by any other user.

Additionally, the client side application 126 may also be configured tooptionally restrict access to the resources 165 by other applicationsexecuted by the client device 120, thereby preventing access to theresources 165 from an application other than the client side application126. In one embodiment, the client side application 126 may monitornetwork traffic between the client device 120 and the distributionserver 150 and identify any data being transmitted between thedistribution server 150 and an application executed by the client device120 other than the client side application 126. The client sideapplication 126 may then determine whether a resource 165 is beingprovided to an application other than the client side application 126executed by the client device 120 and intercept and/or block theincoming resource 165. In one embodiment, the client side application126 may then allow the intercepted resource 165 to be accessible to theuser via a user interface 137 rendered by the client side application126. In other embodiments, the client side application 126 may denyaccess to the intercepted resource 165 by any other application on theclient device 120. Additionally, the client side application 126 may beexecuted to call on other services associated with the resources 165that are executed on the distribution server 150 or another server ordevice accessible to the client side application 126, for instance, atechnical support service that may be executed on the distributionserver 150.

Furthermore, the client side application 126 may be a containerizedapplication that prohibits the resources 165 from being accessed byother applications, prohibits the resources 165 from being transmittedto other applications on the client device 120, and is configurable torestrict the manner of access to the resources 165 within the clientside application 126. The containerized client side application 126 maybe configured to identify metadata associated with the resources 165that specifies that the resources 165 are not authorized fortransmission outside of the containerized application. Examples of suchtransmission restrictions may include restricting cutting, copying, andpasting of the resources 165 while the resources 165 are being accessedby the client side application 126.

The distribution server 150 may comprise, for example, a server computeror any other system providing distribution capability. Alternatively, aplurality of distribution servers 150 may be employed that are arranged,for example, in one or more server banks or computer banks or otherarrangements. For example, a plurality of distribution servers 150together may comprise a cloud computing resource, a grid computingresource, and/or any other distributed computing arrangement. Suchdistribution servers 150 may be located in a single installation or maybe distributed among many different geographic locations. For purposesof convenience, the distribution server 150 is referred to herein in thesingular. Even though the distribution server 150 is referred to in thesingular, it is understood that a plurality of distribution servers 150may be employed in the arrangements as descried herein.

Certain applications and/or other functionality may be executed in thedistribution server 150 according to certain embodiments. Also, certaindata is stored in a data store 153 that is accessible to thedistribution server 150. The data store 153 may be representative of aplurality of data stores, as can be appreciated. The data stored in thedata store 153, for example, is associated with the operation of theapplications and/or functional entities described herein. The data store153 may utilize strong encryption standards to protect the resources 165from unauthorized access. For example, the data store 153 may utilizeSHA-1 (Standard Hash Algorithm) or a similar strong encryption standardcommonly utilized for server-side data storage.

The components executed on the distribution server 150, for example,include the distribution service 174 and other applications, services,processes, systems, engines, or functionality not disclosed in detailherein. The distribution service 174 is executed to provide resources165 stored in the data store 153 to a requesting client device 120 basedon resource grouping identifiers 154 and distribution rules 171, as willbe described. In addition, the distribution service 174 may also acceptnew resources 165 provided by the user of the client device 120, andpreviously provided resources 165 modified by the user of the clientdevice 120, as will be described.

The data store 153 may include resource grouping identifiers 154,resources 165, and/or other data. The resource grouping identifiers 154may represent unique identifiers for previously determined resourcegroupings and are used to determine which resources 165 are transmittedto the user of the client device 106, as will be described. For example,a resource grouping may relate to organizational groups, organizationalroles, geographic locations, and/or any other type of grouping thatrequire access to a type of resource. Each resource grouping identifier154 may be associated with a pairing of at least one of a plurality ofapproved user credentials 156 and at least one of a plurality ofapproved device identifiers 159. In one embodiment, each combination ofapproved user credentials 156 and approved device identifiers 159 may beassociated with more than one of the resource grouping identifiers 154.Additionally, the pairing of approved user credentials 156 and approveddevice identifiers 159 may be associated with a user's organizationalrole and/or capacity. For instance, the pairing of approved usercredentials 156 and the approved device identifiers 159 may bepredetermined by an IT administrator. In another embodiment, the pairingof approved user credentials 156 and the approved device identifiers 159may be automatically associated with the resource grouping identifiers154 based at least upon a user's pay grade, organizational level, statuswithin the organization, and/or any other organizational factor.

Each resource 165 may be associated with a listing of approved resourcegrouping identifiers 168 and a plurality of distribution rules 171. Theresources 165, the approved resource grouping identifiers 168, and thedistribution rules 171 may be stored on the data store 122 or anotherdata store accessible to the client device 120 and/or other storagefacility in data communication with the distribution server 150. Forinstance, the resources 165, approved resource grouping identifiers 168,and the distribution rules 171 may further be stored on an internalemail server, a web-based email server, an internal file server, athird-party hosted file server, a cloud-based server, or a cached localdata store on the client device 120.

In one embodiment, the listing of approved resource grouping identifiers168 includes a plurality of resource grouping identifiers 154 thatregulate access to the respective resource 165, which may bepredetermined by an IT administrator. For instance, the IT administratormay specify which resource grouping identifiers 154 are permitted accessto the respective resource 165. Additionally, the distribution rules 171regulate how a user having the appropriate user credentials 132 anddevice identifier 135 combination may access the respective resource165. For example, in some embodiments, the distribution rules 171 maydescribe a required and/or a permitted state that an accessing clientdevice 120 must satisfy in order for the client device 120 to bepermitted to access to the resource 165. The distribution rules 171 mayinclude but are not limited to hardware requirements, softwarerequirements, configuration requirements, maintenance requirements of aclient device, and/or requirements related to the resource 165.

In one embodiment, hardware requirements may include requirementsassociated with the CPU, memory, power supply, external storage,peripherals, and/or the like. Software requirements may includerequirements associated with the operating system type and version,operating system authenticity and jailbreak/rooted status, installedapplication types and versions, and/or the like. Configurationrequirements may include requirements associated with the configurationof the hardware, software, data encryption methods, transport protocols,and/or the like. Maintenance requirements may include requirementsassociated with the date of last virus scan for the client device 120,the date of the last access of the client device 120 by IT, the date oflast communication between the client device 120 and the distributionserver 150, the date of last tune-up of the client device 120, and/orthe like. Requirements related to the resource 165 may include whetherthe resources 165 may be rendered while the client device 120 is offlineand/or not in communication with the distribution service 174, whetherto permit synchronization of the resources 165 with a remote data store,whether to restrict the resources 165 from being forwarded, whether topermit storing resources 165 locally on the client device 120, whetherthe resources 165 may only be accessed by client devices 120 located atspecified locations, whether the resources 165 may only be accessedduring specified times, and/or the like.

For instance, the resources 165 may be associated with a set ofdistribution rules 171 that include a plurality of location rules 181.In one embodiment, the location rules 181 specify one or more locationsat which a client device 120 may access the resources 165. In anotherembodiment, the location rules 181 specify one or more locationperimeters within which a client device 120 may access the resources165. More specifically, a location perimeter may encompass a location toestablish a buffer area within which the client device 120 is authorizedto access the resources 165 based on its proximity to the location. Asan example, an administrator of the distribution service 174 maydesignate the boundaries of the locations and/or location perimeterswithin which client devices 120 may access the resources 165. Forinstance, the designated boundaries of a location such as a corporateboard meeting room may be smaller than the designated boundaries of alocation such as a football stadium. Similarly, the designatedboundaries of a location perimeter encompassing a corporate boardmeeting room may be smaller than the designated boundaries of a locationperimeter encompassing a football stadium.

Additionally, the resources 165 may be associated with a set ofdistribution rules 171 that include a plurality of time rules 191. Inone embodiment, the time rules 191 specify one or more times when aclient device 120 may access the resources 165. In another embodiment,the time rules 191 specify one or more time windows within which aclient device 120 may access the resources 165. As an example, anadministrator of the distribution service 174 may designate the timeswhen a client device 120 may access the resources 165 and/or maydesignate the time windows within which a client device 120 may accessthe resources 165.

Both the location rules 181 and time rules 191 may further specify thataccess to the associated resources 165 must be terminated once theclient device 120 is no longer compliant with such distribution rules171. The location rules 181 and time rules 191 may specify that accessto the resources 165 is to be terminated by preventing a recipientclient device 120 from accessing the resources 165 on the client device120 while the client device 120 is non-compliant, by removing theresources 165 from the client device 120 once the client device 120becomes non-compliant, and/or terminating access to the resources 165 bysome other approach. For example, the distribution service 174 removesthe resources 165 by transmitting a command to the client sideapplication 126 to block access to the resources 165, delete theresources 165, and/or otherwise terminate access to the resources 165.Additionally, removing of the resources 165 from the client device 120may include removing local copies of the resources 165, links todownloadable copies of the resources 165, downloaded copies of theresources 165, and/or any other copies of the resources 165. Thedistribution service 174 may also instruct the client side application126 to restore the client device 120 to its default state, therebyremoving all data related to the resource 165 from the client device120.

A user operating a client device 120 may wish to access resources 165stored on the distribution server 150. In one embodiment, the user maymanipulate a user interface 137 rendered by the client side application126 to transmit a request 177 for accessing one or more resources 165 onthe distribution server 150. For instance, the user may provide usercredentials 132, such as, a unique user name, a password, biometricdata, and/or other types of user credentials 132 to request access tothe distribution server 150. The client side application 126 maytransmit the request 177 to the distribution service 174. In oneembodiment, the request 177 may include the user credentials 135provided by the user, the device identifier 135 that uniquely identifiesthe client device 120, and/or any other relevant information such as thelocation information 133 specifying the location of the client device120 and time information 143 specifying the current time.

The distribution service 174 receives the request 177 and determineswhether the user is authorized to access the resources 165 from theclient device 120. For instance, the distribution service 174 may use anauthorization approach as described in U.S. application Ser. No.13/316,073 entitled “CONTROLLING ACCESS TO RESOURCES ON A NETWORK,”which is incorporated herein by reference. As another example, thedistribution service 174 may determine that the user is authorized toaccess the resources 165 from the client device 120 based on the usercredentials 132 associated with the user of the client device 120 andthe device identifier 135 associated with the client device 120 that areprovided with the request 177.

Upon determining that the user is authorized to access the resources 165from the client device 120, the distribution server 150 determines whichof the resources 165 to provide to the client device 120. In oneembodiment, the distribution service 174 determines which resources 165to provide based on the resource grouping identifiers 154 associatedwith each resource 165. For instance, the distribution service 174 mayfirst determine which resource grouping identifiers 154 are associatedwith the pairing of user credentials 132 and the device identifier 135included in the request 177. In one embodiment, the distribution service174 parses the listing of approved user credentials 156 and the listingof approved device identifiers 159 of each resource grouping identifier154 to determine whether the respective resource grouping identifier 154is associated with both the user credentials 132 and the deviceidentifier 135.

Next, the distribution service 174 identifies a resource 165 to provideto the user of the client device 120 based on the determined resourcegrouping identifiers 154. In one embodiment, the distribution service174 identifies one or more resources 165 associated with each one of thedetermined resource grouping identifiers 154. In another embodiment, thedistribution service 174 identifies the resource 165 if the resource 165is associated with all of the determined resource grouping identifiers154. Additionally, in another embodiment, the distribution service 174identifies the resource 165 if it is associated with a threshold numberof the resource grouping identifiers 154. The distribution service 174may then provide the identified resources 165 to the client device 120.

In one embodiment, before the identified resources 165 are provided tothe client device 120, the distribution service 174 may encrypt theresources 165 and/or obfuscate the data of the resources 165 in a mannerwhich only the intended recipient may access the resources 165. Forexample, the distribution service 174 may encrypt the resources 165using symmetric encryption and then transmit both the resources 165 andthe decryption key to the client device 120. Alternatively, if thedistribution service 174 determines that the client device 120 has beenpreviously provided with the decryption key associated with thedistribution service 174, then the distribution service 174 may encryptthe resources 165 and transmit the resources 165 to the client device120.

In another embodiment, before the identified resources 165 are providedto the client device 120, the distribution service 174 may additionallydetermine whether the client device 120 satisfies the distribution rules171 associated with each one of the identified resources 165. Forexample, the distribution service 174 may determine whether the deviceprofile 123 describing the state of the client device 120 satisfies thedistribution rules 171 of each identified resource 165. As discussedabove, the device profile 123 may include hardware specifications of theclient device 120, software specifications of the client device 120,version information of various other components of the client device120, location information 133, time information 143, and/or any otherinformation profiling the client device 120. The distribution service174 may, for instance, only transmit resources 165 to client devices 120whose location information 133 indicates that the client device 120satisfies location rules 181 associated with the resources 165.Similarly, the distribution service 174 may only transmit resources 165to client devices 120 whose time information 143 indicates that theclient device 120 satisfies time rules 191 associated with the resources165. In one embodiment, the distribution service 174 may provide theclient device 120 with access to each identified resource 165 if theclient device 120 satisfies all of, or at least a portion of, thedistribution rules 171 associated with each of the identified resources165. Additionally, in another embodiment, the distribution service 174may provide access to the identified resource(s) 165 if the clientdevice 120 satisfies at least a threshold number of the distributionrules 171 associated with each of the identified resources 165.

Responsive to a determination that the client device 120 is in a stateof compliance with the distribution rules 171, the distribution service174 may be further executed to transmit the identified resources 165 tothe client device 120. In one embodiment, the distribution service 174may automatically transmit the identified resources 165 to the clientdevice 120. In another embodiment, the distribution service 174 may makethe identified resources 165 available for download by the client device120 based on a resource qualifier 172 associated with the respectiveresource 165. For instance, the resource qualifier 172 may indicate therespective resource 165 be made available for download to the clientdevice 120. In this example, the user may transmit a request 177 to thedistribution service 174 to download the respective resource 165.

In one embodiment, the state of the client device 120 may have beenmodified between the time the distribution service 174 makes theidentified resource 165 available for download and the time thedistribution service 174 receives the request to download the identifiedresource 165. For example, the client device 120 may have switchedconnectivity from a secured network 110 to an unsecured network 110. Inthis embodiment, the distribution service 174 may determine for a secondtime whether the client device 120 satisfies the distribution rules 171associated with the resources 165. For example, the request 177 todownload transmitted from the client device 120 may include an updateddevice profile 123. The distribution service 174 may make the seconddetermination of whether the client device 120 satisfies thedistribution rules 171 based on the updated device profile 123. Forinstance, the distribution rules 171 may require that the client device120 be connected to a secured network 110 to gain access to the resource165 and the second determination of compliance may reveal that theclient device 120 is connected to an unsecured network 110. Responsiveto the second determination that the client device 120 satisfies thedistribution rules 171 associated with the resources 165, thedistribution service 174 may provide the resources 165 to the clientdevice 120.

In another embodiment, the device profile 123 may be periodicallytransmitted by the client side application 126 to the distributionserver 150. In this embodiment, each time the device profile 123 istransmitted to the distribution server 150, the distribution service 174may determine whether the updated client device 120 satisfies thedistribution rules 171 using the updated device profile 123. Upondetermining that a client device 120 no longer satisfies thedistribution rules 171, the distribution service 174 may be furtherexecuted to temporarily terminate access to the resources 165 by hidingthe presentation of the resources 165 on the client device 120 until theclient device 120 returns to a compliant state, permanently terminateaccess to the resources 165 by deleting the resources 165 from theclient device 120, and/or otherwise terminate access to the resources165. For example, the distribution service 174 may determine that aclient device 120 is no longer satisfies the location rules 181 and/orthe time rules 191 associated with distributed resources 165 based onupdated location information 133 and/or time information 143,respectively. In response, the distribution service 174 may terminateaccess to the resources 165 associated with the location rules 181and/or time rules 191 that are not satisfied by the client device 120.

In another embodiment, the distribution service 174 may transmit thedistribution rules 171 associated with each one of the identifiedresources 165 to the client device 120. For example, the distributionservice 174 may transmit the distribution rules 171 to the client sideapplication 126 for determining whether the client device 120 satisfiesthe distribution rules 171. In one embodiment, the distribution service174 may not determine whether the client device 120 satisfies thedistribution rules 171 associated with each of the identified resources165 and instead permit the client side application 126 to make thisdetermination. For instance, the client side application 126 maydetermine whether the client device 120 satisfies the distribution rules171 associated with a received resource 165 prior to rendering thereceived resource 165 on the display 136.

In another embodiment, the distribution service 174 may transmit thedistribution rules 171 to the client device 120 prior to transmittingthe identified resources 165. The client side application 126 may thendetermine whether the client device 120 satisfies the distribution rules171, as described above. The client side application 126 may thentransmit an indication back to the distribution service 174 of thecompliance status. Responsive to receiving an indication from the clientdevice 120 that the client device 120 satisfies all and/or a sufficientportion of the distribution rules 171 associated with each respectiveresource 165, the distribution service 174 may then transmit theappropriate identified resources 165 to the client device 120.Additionally, the client side application 126 may store the distributionrules 171 in a memory associated with the client device 120, such as thedata store 122. Upon subsequent requests to access the identifiedresource 165, the distribution service 174 may wait to receive anindication from the client side application 126 that the client device120 satisfies the distribution rules 171 associated with the requestedresource 165 before transmitting the resource 165. For example, theclient side application 126 may use the stored distribution rules 171received from a previous request to make the compliance determinationand transmit the request 177.

The distribution service 174 may be further executed to log all activityrelated to the resources 165 for asset tracking purposes. For example,the distribution service 174 may log activities such as transmission ofresources 165, historical data related to the transmission of theresource 165, data related to the rendering of the resources 165 by theclient device 120, data related to a storage location of the resources165, data related to communication with the client device 120, datarelated to resource qualifiers 172 associated with the resources 165,data related to client device 120 compliance with distribution rules171, data related to usage and availability of bandwidth, and/or anyother data related to the resources 165.

In an additional embodiment, the distribution service 174 mayperiodically determine whether the transmitted resources 165 have beenmodified on the client device 120 and synchronize the modified resource165 on the client device 120 with the unmodified resource 165 on thedistribution server 150. For instance, the distribution service 174 maydetermine whether the resource 165 has been modified based on an editdate, modified date, and/or an access date associated with the resource165. In this embodiment, the distribution service 174 may periodicallyrequest to receive the relevant date from the client side application126. Upon receiving the relevant date, the distribution service 174compares the relevant date from the client device 120 with thecorresponding date on the distribution server 150 and determines tosynchronize the respective resources 165 if the two relevant dates donot match. For instance, the distribution service 174 may employ asynchronization approach as is known in the art. In one embodiment, thedistribution service 174 may employ the synchronization approach afterdetermining whether the user is permitted to modify the resource 165 onthe client device 120. In another embodiment, the distribution service174 may remove the resource 165 on the client device 120 uponsynchronizing with the distribution server 150. In another embodiment,the distribution service 174 stores the modified resource 165 in thedata store 153 as one of a plurality of versions of the respectiveresource 165.

In another embodiment, the client side application 126 may bepre-authorized to access at least some of the resources 165 hosted bythe distribution server 150. In such embodiments, the distributionservice 174 may be configured to provide to the client side application126 a listing of all resources 165 available for download by the clientdevice 120 based only on certain embedded authorization data (e.g.,device identifier 135, and/or device profile 123, etc.) and withoutrequiring the client side application 126 to provide additionalauthorization data (e.g., user name and password). For example, thedistribution service 174 may identify resources 165 to include in thelisting by determining which of the resources 165 are associated withdistribution rules 171 that correspond with the device profile 123 ofthe client device 120. As another example, the distribution service 174may provide a listing of resources 165 that may be accessible to clientdevices 120 based at least in part on the location information 133 andthe time information 143 as indicated by the device profile 123 of theclient device 120. In this example, the distribution service 174 maydetermine that a resource 165 is accessible to the client device 120 ifits location information 133 satisfies location rules 181 associatedwith the resources 165 and/or if its time information 143 satisfies timerules 191 associated with the resources 165. The distribution service174 may then allow the client side application 126 to download at leastsome of the available resources 165.

However, one or more of the available resources 165 may be associatedwith a distribution rule 171 that requires additional authorization. Forinstance, the resource 165 may be a document containing sensitiveinformation that requires authorization of a username and password orother additional authorization data. Thus, if the client sideapplication 126 submits a request to download such a resource 165, thedistribution server 174 may prompt the client side application 126 toprovide additional authorization data. In response, the client sideapplication 126 may prompt the user to provide user credentials 132. Inone embodiment, the client side application 126 may transmit the usercredentials 132 and/or the device identifier 135 of the client device120 to the distribution service 174. The distribution service 174 maythen authorize the user to access the sensitive resource 165 using anauthorization approach as described in U.S. application Ser. No.13/316,073 entitled “CONTROLLING ACCESS TO RESOURCES ON A NETWORK,”which is incorporated herein by reference. Upon determining that theuser is authorized to access the sensitive resource 165 from the clientdevice 120, the distribution service 174 may allow the client sideapplication 126 to download the sensitive resource 165.

Next, an exemplary set of user interfaces is discussed in connectionwith FIGS. 2-7, depicting user interfaces that may be displayed as aclient device requests access to the distribution server 150 andreceives any available resources 165, if appropriate. In one embodiment,the user interfaces 137 depicted in FIGS. 2-4 are generated by thedistribution service 174 (FIG. 1) and rendered by the client sideapplication 126 (FIG. 1) on the display 136 (FIG. 1) of the clientdevice 120 (FIG. 1). In another embodiment, the user interfaces 137depicted in FIGS. 2-4 are generated and rendered by the client sideapplication 126 on the display 136. The graphical elements andcomponents that comprise user interfaces 137 of FIGS. 2-4 are presentedby way of example only. Other approaches for presenting the contentdepicted in the exemplary user interfaces 137 and/or for presentingother content for implementing the subject matter described herein willbe readily appreciated by those skilled in the art.

FIG. 2 is an example of a log-in interface 137 a, according to certainembodiments of the present disclosure. The exemplary log-in interface137 a allows a user to provide user credentials 132 (FIG. 1) in order torequest access to the distribution server 150 (FIG. 1). For example, thelog-in interface 137 a may include a group ID field 201, a usernamefield 203, a password field 206, a work offline switch 209, and a loginbutton 213. The user may provide one or more resource groupingidentifiers 154 (FIG. 1) in the group ID field 201, user credentials 132in the username field 203, and a password in the password field 206.Additionally, the user may optionally elect whether to access thedistribution server 150 via an offline mode by activating the workoffline switch 209. For example, the user may wish to access theresources 165 (FIG. 1) that have been previously stored locally on theclient device 120 (FIG. 1), without establishing a current connection tothe distribution service 174 (FIG. 1). Invoking the login button 213transmits a request 177 (FIG. 1) to access the distribution server 150.In one embodiment, the client side application 126 transmits the request177 that may include the user credentials 132, a device identifier 135(FIG. 1) of the client device 120, and a device profile 123 (FIG. 1) ofthe client device 120, as discussed above. As will be appreciated, theclient side application 126 may be configured to access the deviceidentifier 135 and device profile 123 from the data store 122 (FIG. 1).

FIG. 3 is an example of a browsing interface 137 b, according to certainembodiments of the present disclosure. The exemplary browsing interface137 b provides functionality for browsing resources 165 (FIG. 1)accessible to the client device 120 (FIG. 1). In this example, thebrowsing interface 137 b includes a content navigation area 303, aninterface navigation area 306, and a content viewing area 309. Thecontent navigation area 303 may include a plurality of navigationcontrols to browse through the available resources 165 provided to theuser. As an example, the navigation controls may permit the user tobrowse “all content,” “new content,” recent activity,” “favorites,”and/or browse by a category. For example, resources 165 available to theuser and client device 120 may be accessible through one or more of thenavigation controls based on a plurality of resource qualifiers 172(FIG. 1) associated with each of the respective resources 165. Theresource qualifier 172 may indicate that the respective resource 165 ismarked as a “favorite,” for instance.

Additionally, the interface navigation area 306 may include a pluralityof navigation controls to navigate through the interface generated bythe distribution service 174 (FIG. 1). For instance, the navigationcontrols may include a “content” button, a “search” button, a“downloads” button, an “updates” button, and a “settings” button. In oneembodiment, invoking the “content” button may transmit a request 177(FIG. 1) to the distribution service 174 to view all and/or a portion ofthe resources 165 available to the client device 120. Invoking the“search” button may transmit a request 177 to the distribution service174 to search the data store 153 for a specific resource 165. Forinstance, the user may be able to search by a name, genre, type,category, creation date, owner, and/or any other aspect of the resource165. Invoking the “downloads” button may transmit a request 177 to thedistribution service 174 to view and/or otherwise access all previouslydownloaded resources 165 (e.g., previously downloaded by the currentclient device 120 or by other client devices 120 operated by the user).In another embodiment, invoking the “downloads” button may also transmita request 177 to the distribution service 174 to download any resources165 made available to the user. Invoking the “updates” button maytransmit a request 177 to the distribution service 174 to view and/orotherwise access available updates for the client side application 126.Additionally, invoking the “settings” button may transmit a request 177to the distribution service 174 to view, change, and/or otherwise accessany settings and/or preferences associated with the client sideapplication 126.

The content viewing area 309 may include a viewing area for viewing,accessing, manipulating, editing, executing, consuming, and/or otherwiseusing the resource 165 provided by the distribution service 174. In oneembodiment, the resources 165 may be automatically received from thedistribution server 150 and made available for the user in the contentviewing area 309. For example, the distribution service 174 mayautomatically transmit a resource 165 to the client device 120 based onone or more resource qualifiers 172, as discussed above. In anotherembodiment, the user may be presented with a download button to transmita request 177 to download a resource 165 made available by thedistribution service 174. For example, the distribution service 174 mayprovide a resource 165 to be available upon a download request 177 bythe user of the client device 120 based on one or more resourcequalifiers, as discussed above.

FIG. 4 is another example of a user interface 137, denoted herein asuser interface 137 c, according to certain embodiments of the presentdisclosure. The exemplary user interface 137 c depicts a resource 165(FIG. 1) displayed in the content viewing area 309. For instance, theresource 165 may be a document comprising a plurality of pages that maybe navigated using a resource navigation panel 403. In one embodiment,the resource 165 displayed in the content viewing area 309 may be editedby the user, saved locally, saved on a removable drive, saved on a clouddevice, emailed, transmitted via a social network, and/or otherwisemanipulated using tools and functions provided by the client sideapplication 126 (FIG. 1). Additionally, the distribution rules 171associated with the displayed resource 165 may regulate whether theresource 165 may be manipulated, as discussed above. For instance, thedistribution rules 171 may prevent the resource 165 from being edited,emailed and/or transmitted via a social network.

Next, an exemplary set of user interfaces 137 (FIG. 1) is discussed inconnection with FIGS. 5-7, depicting user interfaces 137 that may bedisplayed for a user managing resources 165 (FIG. 1) hosted by thedistribution server 150 (FIG. 1). In one embodiment, the user interfaces137 depicted in FIGS. 5-7 are generated by the distribution service 174(FIG. 1) and rendered by the client side application 126 (FIG. 1) and/ora browser on the display 136 (FIG. 1) of the client device 120 (FIG. 1).In another embodiment, the user interfaces 137 depicted in FIGS. 5-7 aregenerated and rendered by the client side application 126 and/or abrowser on the display 136. The graphical elements and components thatcomprise user interfaces 137 of FIGS. 5-7 are presented by way ofexample only. Other approaches for presenting the content depicted inthe exemplary user interfaces 137 and/or for presenting other contentfor implementing the subject matter described herein will be readilyappreciated by those skilled in the art.

FIG. 5 is an example of a landing interface 137 e for an administratorof the distribution server 150, according to certain embodiments of thepresent disclosure. The exemplary landing interface 137 e includes aresource group indicator 501, navigation area 503, and a documents area506. In one embodiment, the resource group indicator 501 may depict aresource grouping identifier 154 (FIG. 1) currently being managed. As anexample, user interface 137 e depicts the resources 165 associated withthe resource grouping identifier 154 called “Team Kyle.” A drop-downbutton may be associated with the resource group indicator 501 formanaging resources 165 (FIG. 1) associated with other resource groupingidentifiers 154. The navigation area 503 may include a plurality ofnavigation controls that permit the user to manage the content hosted bythe distribution server 150 that is associated with the resourcegrouping identifier 154 depicted by the resource group indicator 501.For example, the navigation controls may include a plurality of buttons,such as a “documents” button, to manage resources 165 associated withthe “Team Kyle” resource grouping identifier 154.

Additionally, the documents area 506 includes a listing of resources 165that are associated with the resource grouping identifier 154 depictedby the resource group indicator 501. In one embodiment, the resources165 may be presented in a table 509 where each row in the table includesidentifying information for each of the respective resources 165. Forinstance, the table may include a name of the resource 165, a type ofthe resource 165, a brief description of the resource 165, an owner ofthe resource 165, an effective date of the resource 165, and a date oflast modification of the resource 165. Additionally, a plurality ofmanagement buttons 513 may be presented for each resource 165. Forinstance, the management buttons 513 may permit the administrator toedit the resource qualifiers 172 (FIG. 1) associated with the resource165, add version information, view a listing of resource groupingidentifiers 154 with access to the respective resource 165, download acopy of the resource 165, and remove the resource 165 from being hostedby the distribution server 150.

In one embodiment, the documents area 506 may also include an “adddocument” button 516, a “bulk import” button 519, and sorting options523. For instance, invoking the “add document” button 516 may transmit arequest to the distribution service 174 to add new resources 165 to behosted by the distribution server 150, as will be described with respectto FIGS. 6 and 7. Additionally, invoking the “bulk import” button 519may transmit a request 177 (FIG. 1) to the distribution service 174 tosimultaneously add and/or import a plurality of resources 165, as can beappreciated. Further, the sorting options 523 may include a plurality ofoptions for the administrator to transmit a request 177 to sort theresources 165 presented in the table 509, such as according to aresource category, a resource type and/or any other sorting option.

FIG. 6 is an example of a user interface 137 f that allows anadministrator to add a new resource 165 to be hosted by the distributionserver 150, according to certain embodiments of the present disclosure.For instance, the user interface 137 f includes a grouping field 603, aresource field 606, an upload button 609, and a continue button 613. Inone embodiment, the administrator may provide one or more resourcegrouping identifiers 154 (FIG. 1), in the grouping field 603, thatpermit users and client devices 120 to access the new resource 165 to beadded. Additionally, an administrator may indicate a location of the newresource 165 to be added in the resource field 606. For example, theadministrator may specify the location of the new resource 165 to beadded as residing on a SharePoint sever, a cloud storage account, and/orany other storage system accessible to the client device 120 and/or thedistribution server 150. Invoking the upload button 609 transmits arequest 177 (FIG. 1) to the distribution service 174 to upload theresource 165 specified in the resource field 606 and to associate itwith the resource grouping identifiers 154 specified in the groupingfield 603. Invoking the continue button 613 may transmit a request 177to the distribution service 174 to advance to another user interface137, such as the interface described with respect to FIG. 7.

FIG. 7 is an example of a user interface 137 g that allows anadministrator to specify distribution rules 171 for a resource 165,according to certain embodiments of the present disclosure. In oneembodiment, the user interface 137 g includes a rules navigation panel703, a rules specification area 706, a save button 709, and a resetbutton 713. The rules navigation panel 703 may include a plurality oftabs for specifying various types of distribution rules 171. Forexample, the tabs may include an “information” tab for providing generalinformation related to the resource 165, a “details” tab for providingspecific details related to the resource 165, a “previous versions” tabfor providing distribution rules 171 related to a previous version ofthe resource 165, a “security” tab for providing security measures suchas encryption and/or write capability for the resource 165, an“assignment” tab for providing ownership criteria related to theresource 165, and a “deployment” tab for specifying whether the resource165 will be made available for download or automatically transmitted toa user upon request. Activation of each tab will change the userinterface 137 g to display fields, buttons, menus, and/or othercomponents for inputting the appropriate details.

In one embodiment, invoking one of the tabs in the navigational panel703 may transmit a request 177 (FIG. 1) to the distribution server 150to specify distribution rules 171 associated with the respective type.As shown in FIG. 7, the rules specification area 706 depicts a pluralityof fields for specifying distribution rules 171 related to theinformation tab. For example, the fields in the rules specification area706 may include a field for specifying a name, a location, a version, adescription, an importance level, a resource grouping identifier 154,and/or any other information related to the new resource 165.Additionally, invoking the save button 709 may transmit a request 177 tothe distribution service 174 to save the distribution rules 171specified via the user interface 137 g. Invoking the reset button 713may transmit a request 177 to the distribution service 174 to reset thedistribution rules 171 associated with a particular resource.

FIG. 8 is a flowchart illustrating exemplary functionality performed bythe distribution service 174 (FIG. 1) according to certain embodiments.It is understood that the flowchart of FIG. 8 provides merely an exampleof the many different types of functional arrangements that may beemployed to implement the operation of the distribution service 174 asdescribed herein. As an alternative, the flowchart of FIG. 8 may beviewed as depicting an example of steps of a method implemented in thedistribution server 150 (FIG. 1) according to one or more embodiments.

Beginning with step 803, the distribution service 174 receives a request177 (FIG. 1) from a client device 120 (FIG. 1) to access resources 165(FIG. 1) hosted by the distribution server 150. In one embodiment, therequest 177 may include a device identifier 135 (FIG. 1) associated withthe client device 120 and user credentials 132 (FIG. 1) of the useroperating the client device 120. In another embodiment, the request 177may additionally include a device profile 123 (FIG. 1) and/orinformation related to the device profile 123 that describes a state ofthe client device 120.

Next, in step 806, the distribution service 174 determines whether theclient device 120 and the user operating the client device 120 areauthorized to access the resources 165 hosted by distribution service174. In one embodiment, the distribution service 174 may authorize theuser and client device 120 pairing according to the approach describedin application Ser. No. 13/316,073 entitled “CONTROLLING ACCESS TORESOURCES ON A NETWORK,” as described above. If the distribution service174 determines that the user may not access the resources 165 from theclient device 120, then the distribution server 150 advances to step 809and notifies the user. For instance, the distribution service 174 maytransmit a notification indicating that the user is not authorized toaccess the resources 165 from the client device 120.

Returning to step 806, if the distribution service 174 determines thatthe user is authorized to access the resources 165, then thedistribution service 174 proceeds to step 810 and provides a userinterface 137 (FIG. 1) to the client device 120. For instance, thedistribution service 174 may provide a browsing interface 137 b as shownin FIG. 3 to the client device 120. Then, in step 813, the distributionservice 174 determines the resource grouping identifiers 154 of theresources 165 accessible by the user from the client device 120. In oneembodiment, the distribution service 174 determines the resourcegrouping identifiers 154 based on the user credentials 132 of the userand the device identifier 135 of the client device 120. For instance,each resource grouping identifier 154 may be associated with a pairingof user credentials 132 and a device identifier 135. The distributionservice 174 may determine one or more resource grouping identifiers 154associated with the pairing of user credentials 132 and the deviceidentifier 135, as described above.

Then, in step 816, the distribution service 174 identifies the resources165 that are associated with the determined resource groupingidentifiers 154. In one embodiment, each resource 165 may be associatedwith more than one resource grouping identifier 154. Additionally, eachresource grouping identifier 154 may have an association with more thanone resource 165, as described above. Upon identifying all of theresources 165 associated with the determined resource groupingidentifiers 154, the distribution service 174 proceeds to step 819 anddetermines whether the client device 120 from which the request 177 wasreceived complies with the distribution rules 171 associated with eachone of the identified resources 165. In one embodiment, the distributionservice 174 determines whether the client device 120 is compliant basedon the device profile 123 associated with the client device 120. Forinstance, the distribution service 174 may have received the deviceprofile 123 in conjunction with the request 177. As another example, thedistribution service 174 may determine whether the location information133 (FIG. 1) associated with the client device 120 satisfies thelocation rules 181 associated with an identified resource 165.

If the distribution service 174 determines that the client device 120does not comply with any of the distribution rules 171 associated witheach one of the resources 165, then the distribution service 174proceeds to step 809 and transmits a notification of noncompliance tothe client device 120. In one embodiment, the distribution service 174may determine that the client device 120 complies with the distributionrules 171 of a portion of the identified resources 165. In this example,the distribution service 174 may transmit a notification ofnoncompliance to the client device 120 that includes a name of theidentified resources 165 and a message that the client device 120 is notauthorized to receive due to noncompliance with the distribution rules171 associated with the identified resource 165.

Returning to step 819, if the distribution service 174 determines thatthe client device 120 complies with the distribution rules 171 of alland/or a portion of the identified resources 165, the distributionservice 174 proceeds to step 823 and transmits the identified resources165 associated with the distribution rules 171 with which the clientdevice 120 is in compliance. In one embodiment, the distribution service174 automatically transmits the identified resources 165 that the clientdevice 120 is authorized to receive based on compliance withdistribution rules 171. In another embodiment, the distribution service174 may make available for download the identified resources 165 thatthe client device 120 is authorized to receive. For instance, the clientdevice 120 may receive an indication that the resource 165 is availablefor download and may transmit a request 177 to the distribution service174 for downloading the applicable resource 165. Upon receiving therequest, the distribution service 165 may transmit the resource 165 tothe client device 120. Additionally, in another embodiment, thedistribution rules 171 associated with the transmitted resources 165 maybe transmitted in conjunction with the resources 165. For instance, aclient side application 126 (FIG. 1) on the client device 120 mayperiodically determine whether the client device 120 remains compliantto access the received resources 165, as described above.

FIG. 9 is a flowchart illustrating exemplary functionality performed bya client side application 126 (FIG. 1) according to certain embodiments.It is understood that the flowchart of FIG. 9 provides merely an exampleof the many different types of functional arrangements that may beemployed to implement the operation of the client side application 126as described herein. As an alternative, the flowchart of FIG. 9 may beviewed as depicting an example of steps of a method implemented in theclient device 120 (FIG. 1) according to one or more embodiments.

Beginning with step 903, the client side application 126 transmits arequest 177 (FIG. 1) to the distribution service 174 (FIG. 1) to accessresources 165 (FIG. 1). In one embodiment, the client side application126 may include user credentials 132 (FIG. 1) of a user and a deviceidentifier 135 (FIG. 1) of the client device 120 in conjunction with therequest 177. For instance, the client side application 126 may promptthe user of the client device 120 to provide the user credentials 132for requesting the access and may access the device identifier 135 froma local data store 122 or from the device hardware of the client device120.

Then, in step 906, the client side application 126 receives a pluralityof sets distribution rules 171 (FIG. 1) from the distribution server 150(FIG. 1). In one embodiment, the client side application 126 may receivethe sets of distribution rules 171 if the user and the client device 120are authorized to access the resources 165. For instance, the user andthe client device 120 may be authorized based on the user credentials132 and the device identifier 135 transmitted in conjunction with therequest 177. In addition, each of the received sets of distributionrules 171 may be associated with one of a plurality of resources 165that are determined to be accessible to the user and the client device120. For instance, the resources 165 accessible to the user and theclient device 120 may be determined based on a plurality of resourcegrouping identifiers 154 (FIG. 1), wherein the resource groupingidentifiers 154 are determined based on the user credentials 132 of theuser and the device identifier 135 of the client device 120, asdescribed above.

Upon receiving the distribution rules 171, the client side application126, in step 909, determines whether the client device 120 is compliantwith the sets of distribution rules 171 associated with the resources165 accessible to the user and client device 120 pairing. In oneembodiment, the client side application 126 may determine whether theclient device 120 is compliant with the sets of distribution rules 171based on the device profile 123 (FIG. 1) of the client device 120, asdescribed above. If the client side application 126 determines that theclient device 120 is not compliant with a portion and/or all of the setsof distribution rules 171, then the client side application 126 proceedsto step 913 and renders a notice of non-compliance on a display 136(FIG. 1) of the client device 120. In one embodiment, the notice mayidentify a plurality of resources 165 associated with the sets ofdistribution rules 171 that resulted in the non-compliance.Additionally, if the client side application 126 determines that theclient device 120 is not compliant with any of the sets of distributionrules 171, the client side application may transmit a notification tothe distribution service 174 indicating that the client device 120 isnon-compliant.

Returning to step 909, if the client side application 126 determinesthat the client device 120 is compliant with all and/or a portion of thesets of distribution rules 171, then the client side application 126proceeds to step 916 and transmits an notification of compliance to thedistribution service 174. In one embodiment, if the client sideapplication 126 determines that the client device 120 is compliant withonly a portion of the sets of distribution rules 171, then thenotification may include an indication of the sets of distribution rules171 with which the client device 120 complies.

Then, in step 919, the client side application 126 receives theresources 165 associated with the distribution rules 171 with which theclient device 120 complies. In one embodiment, the resources 165 may beautomatically received by the client device 120. In another embodiment,the client side application 126 may receive an indication that theresources 165 are available for download. In step 923, the receivedresources 165 are rendered on the display 136. In one embodiment, theclient side application 126 may render a notification to the user thatthe resources 165 are available for download. Then, upon receiving arequest 177 from the user to download the resources 165, the client sideapplication 126 may download the resources 165 from the distributionserver 150 and render the downloaded resources 165 on the display 136.

FIG. 10 illustrates a second networked environment 1000 according tovarious embodiments, similar to the networked environment 100 of FIG. 1.Here, the network 110 may also be or include, for example, any type ofwireless network such as a wireless local area network (WLAN), awireless wide area network (WWAN), or any other type of wirelessnetwork. Additionally, the network 110 may be or include the Internet,intranets, extranets, microwave networks, satellite communications,cellular systems, PCS, infrared communications, global area networks, orother suitable networks, etc., or any combination of two or more suchnetworks. For example, the network 110 may include satellitecommunications such as passive communication systems, activecommunication systems, global positioning systems, and multibeamcommunication systems. The network 110 facilitates transmittingresources 165 (FIG. 1) between a distribution server 150 and clientdevices 120, such as client devices 120 a, 120 b, and 120 c. Morespecifically, the network 110 facilitates transmitting resources 165between a distribution service 174 (FIG. 1) executed on the distributionserver 150 and a client side application 126 (FIG. 1) executed on eachof the client devices 120. The client side application 126 may be“containerized” to restrict the resources 165 from being utilized in anunauthorized manner, such as transmitting the resources 165 outside ofthe containerized environment of the client side application 126. Inparticular, the administrator of the distribution service 174 mayconfigure one or more restrictions to control the manner of whichresources 165 may be utilized within the containerized client sideapplication 126.

The network 110 may also facilitate the identification of locationinformation 133 (FIG. 1) describing the location of client devices 120by employing one or more client device 120 positioning methodologieswell known in the art. In one embodiment, the location of a clientdevice 120 may be identified based on the client device's detection ofthe presence of a transmission beacon. Transmission beacons may includeWi-Fi beacons, Bluetooth beacons, microwave beacons, infrared beacons,ultrasound beacons, cellular beacons, satellite beacons, and/or othertypes of beacons related to transmission. The location of a transmissionbeacon may be known, as many transmission beacon types require fixedphysical installations. The characteristics of a transmission beacon mayalso be known such as its identity and hardware specifications, whichmay indicate the magnitude of the transmission range of the transmissionbeacon. As a client device 120 must be within the transmission range ofa transmission beacon for the client device 120 to detect the presenceof the transmission beacon, the location of the client device 120 may beidentified based on the location and specifications of the detectedtransmission beacon.

In another embodiment, the location of a client device 120 may beidentified based on the client device's detection of the signal strengthof more than one transmission beacon, known well in the art as“triangulation.” In particular, the two-dimensional location of a clientdevice 120 may be identified by comparing the signal strength of twotransmission beacons detected by the client device 120. Similarly, thethree-dimensional location of a client device 120 may be identified bycomparing the signal strength of three transmission beacons detected bythe client device 120.

In a further embodiment, the location of a client device 120 may beidentified based on the detection of the client device 120 by thenetwork 110. In particular, the network 110 may include one or moretransmission beacons. The transmission beacons may provide the network110 with an indication of which client devices 120 are connected to thetransmission beacon. The transmission beacons may further provide thenetwork 110 with an indication of the characteristics of thetransmission beacon such as its identity and hardware specifications,which may indicate the transmission range of the transmission beacon.Thus, the location of a client device 120 may be identified by thenetwork 110 by determining which transmission beacon the client device120 is utilizing and the maximum distance that the client device 120 maybe from the transmission beacon based on the characteristics of thetransmission beacon.

In yet another embodiment, the location of a client device 120 may beidentified based on the known previous location of the client device 120and the known movements of the client device 120, which is well known inthe art as “dead reckoning.” The location of a client device 120 mayhave been previously identified based on any of the aforementionedclient device 120 positioning methodologies. Additionally, the clientdevice 120 may be capable of determining any movement of the clientdevice 120 from the previously identified location of the client device120. For example, the client device 120 may include movement sensorscapable of determining the rate of movement of the client device 120,the duration of movement of the client device 120, and the direction ofmovement of the client device 120. Thus, the client device 120 may usethe data obtained from the movement sensors to identify the location ofthe client device 120 based on its movement from its previouslyidentified location.

In yet a further embodiment, the location of the client device 120 maybe identified based on the device profile 123 associated with the clientdevice 120. More specifically, the device profile 123 may hold anindication of the location of the client device 120 that was obtained bythe device profile 123 on any of the aforementioned client device 120positioning methodologies. Alternatively, the indication of the locationof the client device 120 provided by the device profile 123 may beidentified based on data obtained from satellites and/or GlobalPositioning Systems.

Additionally, FIG. 10 depicts an authorized location 1001 and anauthorized perimeter 1002 that encompasses the authorized location 1001.The authorized location 1001 and the authorized perimeter 1002 may bedetermined from the location rules 181 (FIG. 1). In particular, theauthorized location 1001 and authorized perimeter 1002 may specify oneor more locations where client devices 120 may access resources 165. Theadministrator of the distribution service 174 may specify the boundariesof an authorized location 1001 and/or authorized perimeter 1002. Theadministrator may define the boundaries of the authorized location 1001and authorized perimeter 1002 by specifying one or more geographiccoordinates that encompass the authorized location 1001 and authorizedperimeter 1002. In one embodiment, the geographic coordinates mayspecify the center of an authorized location 1001 and/or authorizedperimeter 1002. The administrator may further specify the magnitude of aradius that extends from the central coordinate pair to establish aboundary encompassing the authorized location 1001 and/or authorizedperimeter 1002. In another embodiment, coordinates may specify boundarypoints for an authorized location 1001 and/or authorized perimeter 1002.The distribution service 174 may be configured to establish a boundaryfor the authorized location 1001 and/or authorized perimeter 1002 byconnecting coordinates. For example, the distribution service 174 mayestablish a rectangle shaped boundary, a square shaped boundary, and/ora boundary of another shape based on an administrator's input ofcoordinates. Alternatively, the distribution service 174 may execute adrawing tool that allows an administrator to visually designate theboundaries of an authorized location 1001 and/or authorized perimeter1002 on a map, a floor plan, and/or other layout.

The networked environment 1000, including the authorized location 1001and the authorized perimeter 1002, provide for heightened security oflocation-sensitive resources 165. In one embodiment, the distributionservice 174 administrator may specify that resources 165 with highsensitivity may only be accessed by client devices 120 located withinthe authorized location 1001. In another embodiment, the administratormay specify that resources 165 with low sensitivity may be accessed byclient devices 120 located within either the authorized location 1001 orthe authorized perimeter 1002. The magnitude of the authorized perimeter1002 may be based at least in part on the type of authorized location1001. For example, an authorized perimeter 1002 encompassing a largeauthorized location 1001, such as a football stadium, may be larger thanan authorized perimeter 1002 encompassing a small authorized location1001, such as a corporate board meeting room. Additionally, themagnitude of the authorized perimeter 1002 may be based at least in parton the sensitivity of associated resources 165. For example, authorizedperimeters 1002 associated with resources 165 with high sensitivity maybe smaller than authorized perimeters 1002 associated with resources 165with low sensitivity.

As described with regard to FIG. 1, client devices 120 may receiveaccess to resources 165 from the distribution server 150 if the clientdevices 120 are both authorized to communicate with the distributionserver 150 and comply with one or more distribution rules 171 (FIG. 1)associated with the resources 165. The client devices 120 a, 120 b, and120 c of the networked environment 1000 may be similar with respect totheir hardware configurations, software configurations, and maintenancerecords. Client devices 120 a, 120 b, and 120 c may further have usercredentials 132 (FIG. 1) and device identifiers 135 (FIG. 1) that areauthorized for access to the distribution service 174. Nevertheless,client devices 120 a, 120 b, and 120 c may not be equally authorized foraccess to resources 165 based on one or more location rules 181associated with the resources 165.

As an example, the location rules 181 may specify that client devices120 located within the authorized location 1001 may be authorized foraccess to a “high sensitivity” subset of resources 165, client devices120 located within the authorized perimeter 1002 may be authorized foraccess to a “medium sensitivity” subset of resources 165, and clientdevices 120 located outside of both the authorized location 1001 andauthorized perimeter 1002 may be authorized for access to a “lowsensitivity” subset of resources 165. Additionally, the location rules181 may specify that client devices 120 authorized for access to the“high sensitivity” subset resources 165 are further authorized foraccess to both the “medium sensitivity” and “low sensitivity” subsets ofresources 165 and that client devices 120 authorized for access to the“medium sensitivity” subset of resources 165 are further authorized foraccess to the “low sensitivity” subset of resources 165. Thus, clientdevices 120 that are authorized for access to resources 165 associatedwith more restrictive location rules 181 may further be authorized foraccess to resources 165 associated with less restrictive location rules181. Additionally, the location rules 181 may specify that the resources165 must be deleted from client devices 120 that cease to comply withthe location rules 181 associated with such resources 165. While in someexamples, client devices 120 located outside of both the authorizedlocation 1001 and authorized perimeter 1002 to be authorized for accessto a “low sensitivity” subset of resources 165, it is to be understoodthat a more restrictive security schema may prohibit client devices 120located outside of both the authorized location 1001 and authorizedperimeter 1002 from accessing any resources 165.

In one embodiment, the client side application 126 executed by theclient device 120 a may transmit a request 177 (FIG. 1) for access toresources 165 to the distribution service 174 executed by thedistribution server 150. As described with regard to FIG. 1, the accessrequest 177 may include user credentials 132 (FIG. 1) and a clientdevice identifier 135 (FIG. 1) associated with the client device 120 a.The access request 177 may further include location information 133(FIG. 1) specifying the location of the client device 120 a. Aspreviously described, the client side application 126 may identify thelocation information 133 associated with the client device 120 a fromthe device profile 123 associated with the client device 120 a, and thelocation information 133 may be identified based at least in part onnetwork 110 data. In another embodiment, the distribution service 174may identify the location of the client device 120 a based at least inpart on data associated with the network 110. On a first request foraccess, the distribution service 174 may determine whether the clientdevice 120 a is authorized to access the distribution server 150 basedat least in part on the user credentials 132 and device identifier 135of the request 177. In this example, the user credentials 132 and deviceidentifier 135 associated with the client device 120 a are authorized,and the distribution service 174 may determine that the client device120 a is authorized to access the distribution server 150.

Next, the distribution service 174 may determine which, if any, of thesubsets of resources 165 that the client device 120 a is authorized toaccess. More specifically, the distribution service 174 may authorizethe client device 120 a for access to resources 165 associated withlocation rules 181 that are satisfied by the location information 133associated with the client device 120 a. The location information 133associated with the client device 120 a may indicate that the clientdevice 120 a is located within the authorized location 1001. If thedistribution service 174 determines that the client device 120 a islocated within the authorized location 1001, the distribution service174 may then authorize the client device 120 a to access the “highsensitivity” subset of resources 165, the “medium sensitivity” subset ofresources 165, and the “low sensitivity” subset of resources 165. Thedistribution service 174 may, for example, transmit the “highsensitivity,” “medium sensitivity,” and “low sensitivity” subsets ofresources 165 to the client device 120 a to provide the client device120 a with access to the resources 165.

While the client device 120 a may be authorized to access the resources165 upon receipt from the distribution service 174, the client device120 a may cease to be authorized based on any changes in its location.To this end, the client side application 126 may monitor the locationinformation 133 associated with the client device 120 a to determinewhether the client device 120 a remains compliant with the locationrules 181 associated with the resources 165. In one embodiment, in theevent that the client device 120 a fails to comply with some or all ofthe location rules 181, the client side application 126 may terminateaccess to the resources 165 in accordance with the location rules 181 bypreventing the resources 165 from being accessed by the client device120 a while the location rules 181 are not satisfied. For example, theresources 165 may be configured to be inaccessible while the locationrules 181 are not satisfied by the client device 120 a and may befurther configured to be unlocked while the location rules 181 aresatisfied by the client device 120 a. In another embodiment, in theevent that the client device 120 a fails to comply with some or all ofthe location rules 181, the client side application 126 may terminateaccess to the resources 165 in accordance with the location rules 181 bydeleting the resources 165 from the client device 120 a.

For example, if the client side application 126 determines that theclient device 120 a remains in its initial location, the client sideapplication 126 may continue to provide access to each of the subsets ofresources 165 on the client device 120 a. However, if the client sideapplication 126 determines that the current location of the clientdevice 120 a is no longer in its initial location, the client sideapplication 126 may determine whether the client device 120 a isauthorized to access the resources 165 based on the current location ofclient device 120 a. If the client device 120 a remains located withinthe authorized location 1001, then the client side application 126 maycontinue to provide access to each of the subsets of resources 165. Ifthe client device 120 a is currently located within the authorizedperimeter 1002, then the client side application 126 may provide accessto the “medium sensitivity” and “low sensitivity” subsets of resources165 and may remove access to the “high sensitivity” subset of resources165, as may be indicated by the location rules 181 associated with therespective resources 165. Finally, if the client device 120 a is neitherlocated within the authorized location 1001 nor the authorized perimeter1002, then the client side application 126 may provide access to the“low sensitivity” subset of resources 165 and may remove access to the“high sensitivity” and “medium sensitivity” subsets of resources 165. Inanother embodiment, the client side application 126 may delete and/orotherwise make inaccessible the “low sensitivity” subsets of resources165 from the client device 120 a if the client device 120 a is neitherlocated within the authorized location 1001 nor the authorized perimeter1002.

In another embodiment, the client side application 126 executed by theclient device 120 b may transmit a request 177 for access to resources165 to the distribution service 174 that may include user credentials132, a client device identifier 135, and location information 133related to the location of the client device 120 b. As previouslydiscussed, the location information 133 may be identified from thedevice profile 123 of the client device 120 b or based at least in parton data associated with the network 110. On a first request for access,the distribution service 174 may determine that the client device 120 bis authorized to access the distribution server 150 as the usercredentials 132 and device identifier 135 associated with the clientdevice 120 b are authorized. The distribution service 174 may furtherdetermine whether the client device 120 b is authorized to accessresources 165 based on the location rules 181 associated with theresources 165. The location information 133 associated with the clientdevice 120 b may indicate that the client device 120 b is located withinthe authorized perimeter 1002. Accordingly, the distribution service 174may authorize the client device 120 b to access the “medium sensitivity”and “low sensitivity” subsets of resources 165; for example, thedistribution service 174 may transmit the “medium sensitivity” and “lowsensitivity” subsets of resources 165 to the client device 120 b toprovide the client device 120 b with access to the “medium sensitivity”and “low sensitivity” subsets of the resources 165.

While the client device 120 b may be authorized to access the resources165 upon receipt, the client device 120 b may cease to be authorizedbased on changes to its location. To this end, the client sideapplication 126 may monitor the location information 133 associated withthe client device 120 b to determine whether the client device 120 bremains compliant with the location rules 181 associated with theresources 165. In one embodiment, if the client side application 126determines that the client device 120 b remains in its initial location,then the client side application 126 may continue to provide access tothe “medium sensitivity” and “low sensitivity” resources 165. In anotherembodiment, if the client side application 126 determines that clientdevice 120 b is no longer in its initial location, then the client sideapplication 126 may further determine whether client device 120 b isauthorized to access resources 165 based on the current location ofclient device 120 b. For example, if the client device 120 b remainslocated within the authorized perimeter 1002, then the client sideapplication 126 may continue to provide access to the “mediumsensitivity” and “low sensitivity” subsets of resources 165. If theclient device 120 b is now located within the authorized location 1001,then the client side application 126 may continue provide access to the“medium sensitivity” and “low sensitivity” subsets of resources 165 andmay transmit a request 177 to the distribution service 174 to access the“high sensitivity” subset of resources 165. Finally, if the clientdevice 120 b is now neither located within the authorized location 1001nor the authorized perimeter 1002, the client side application 126 maycontinue to provide access to the “low sensitivity” subset of resources165 and may delete the “medium sensitivity” subset of resources 165 fromclient device 120 b.

In a further embodiment, the client side application 126 executed byclient device 120 c may transmit a request 177 for access to resources165 to the distribution service that may include user credentials 132, aclient device identifier 135, and location information 133 specifyingthe location of the client device 120 c. As previously discussed, thelocation information 133 may be identified from the device profile 123of the client device 120 c or based at least in part on data associatedwith the network 110. On a first request for access, the distributionservice 174 may determine that the client device 120 c is authorized toaccess the distribution server 150 as the user credentials 132 anddevice identifier 135 associated with the client device 120 c areauthorized. The distribution service 174 may further determine whetherthe client device 120 c is authorized to access resources 165 based onthe location rules 181 associated with the resources 165. The locationinformation 133 associated with the client device 120 c may indicatethat the client device 120 c is neither located within the authorizedlocation 1001 nor located within the authorized perimeter 1002.Accordingly, the distribution service 174 may authorize the clientdevice 120 b to access the “low sensitivity” subset of resources 165;for example, the distribution service 174 may transmit the “lowsensitivity” subset of resources 165 to the client device 120 c toprovide the client device 120 c with access to the “low sensitivity”subset of the resources 165.

While the client device 120 c may be authorized to access the resources165 upon receipt, the client device 120 c may cease to be authorizedbased on changes to its location. To this end, the client sideapplication 126 may monitor the location information 133 associated withthe client device 120 c to determine whether the client device 120 cremains compliant with the location rules 181 associated with theresources 165. In one embodiment, if the client side application 126determines that the client device 120 c remains in its initial location,then the client side application 126 may continue to provide access tothe “low sensitivity” resources 165. In another embodiment, if theclient side application 126 determines that client device 120 c is nolonger in its initial location, then the client side application 126 mayfurther determine whether client device 120 c is authorized to accessresources 165 based on the current location of client device 120 c. Forexample, if the client device 120 c is neither located within theauthorized location 1001 nor located within the authorized perimeter1002, then the client side application 126 may continue to provideaccess to “low sensitivity” subset of resources 165. If the clientdevice 120 c is now located within the authorized location 1001, thenthe client side application 126 may continue to provide access to the“low sensitivity” subset of resources 165 and may transmit a request 177to the distribution service 174 to access the “high sensitivity” and“medium sensitivity” subsets of resources 165. Finally, if the clientdevice 120 b is now located within the authorized perimeter 1002, thenthe client side application 126 may continue to provide access to the“low sensitivity” subset of resources 165 and may transmit a request 177to the distribution service 174 to access the “medium sensitivity”subset of resources 165.

In another embodiment, the resources 165 accessible to the client device120 may be determined based at least in part on the time rules 181 (FIG.1). For example, the network 110 may provide time information 143(FIG. 1) describing the current time associated with client devices 120.In one embodiment, time information 143 specifying the current timeassociated with client devices 120 in communication with the network 110may be identified from the device profiles 123 of the respective clientdevices 120. The device profile 123 may include an indication of thetime set by the user of the client device 120. Additionally, the deviceprofile 123 may include an indication of the time provided to the clientdevice 120 by an application executed by the client device 120, such asan FM radio application or Atomic Clock application. Moreover, thedevice profile 123 may include an indication of the time provided to theclient device 120 by the network 110 itself, such as a CDMA network,GSM, and/or other cellular network 110 that may provide the time forclient devices 120 communicating over such network 110. Furthermore, thedevice profile 123 may include an indication of the time provided to theclient device 120 by a server accessible over the network 110, such as aheartbeat server and/or a time server.

In addition, the time information 143 specifying the current timeassociated with client devices 120 on the network 110 may be identifiedbased at least in part on the location information 133 associated withthe client devices 120. For instance, if the current time in Atlanta,Ga. is 1 PM, then the location information 133 specifying that a clientdevice 120 is located in Atlanta, Ga. may be correlated with timeinformation 143 specifying that the current time associated with theclient device is 1 PM. By employing such a location-based timedetermination methodology, the settings of a client device 120 cannot bemanipulated to gain an/or prolong access to resources 165. For instance,a user of a client device 120 might seek to prolong access to resources165 by rolling back the set time of the client device 120 to a time whenthe client device 120 was authorized.

The distribution service 174 administrator may configure the time rules191 to restrict access to resources 165 with “high sensitivity” toclient devices 120 whose current time corresponds to a single authorizedtime. The distribution service 174 administrator may further configurethe time rules 191 to restrict access to resources 165 with “mediumsensitivity” to client devices 120 whose current time is within anauthorized time window, i.e. a collection of sequenced authorized times.The magnitude of the authorized window may be based at least in part onthe sensitivity of associated resources 165; thus, authorized windowsassociated with highly time sensitive resources 165 may be smaller inmagnitude than authorized windows associated with resources 165 oflesser time sensitivity. For example, the time rules 191 may specifythat the resources 165 may only be accessed by client devices 120 whilethe current time is between 12:01 PM and 1 PM. Additionally, thedistribution service 174 administrator may configure the time rules 191to require that access to the resources 165 be removed from clientdevices 120 that do not satisfy the time rules 191. Furthermore, thedistribution service 174 administrator may configure the time rules 191to permit the resources 165 to remain stored in an inaccessible formaton incompliant client devices 120 that are located within the authorizedlocation 1001 but require that the resources 165 be deleted fromincompliant client devices 120 that are located outside of theauthorized location 1001.

As an example, the authorized location 1001 may correspond to a BoardRoom in Atlanta, Ga., the authorized perimeter 1002 may correspond tothe city of Atlanta, Ga., and the area outside of the authorizedlocation 1001 and authorized perimeter 1002 may correspond to the cityof Chicago, Ill. The Board Room in Atlanta, Ga. and the city of Atlanta,Ga. may both reside in the Eastern Time Zone, and the city of Chicago,Ill. may reside in the Central Time Zone. Thus, client devices 120located within the authorized location 1001 and authorized perimeter1002 may be associated with time information 143 specifying that thecurrent time associated with such client devices 120 is the current timein the Eastern Time Zone. Similarly, client devices 120 located outsideof the authorized location 1001 and authorized perimeter 1002 may beassociated with time information 143 specifying that the current timeassociated with such client devices 120 is the current time in theCentral Time Zone. Referring to FIG. 10, if the current time in theEastern Time Zone is 1 PM and the current time in the Central Time Zoneis 12 PM, then the time information 143 associated with the clientdevice 120 a may be 1 PM, the time information 143 associated with theclient device 120 b may be 1 PM, and the time information 143 associatedwith the client device 120 c may be 12 PM.

In one embodiment, the client side application 126 executed by theclient device 120 a may transmit a request 177 for access to resources165 to the distribution service 174 that may include user credentials132, a client device identifier 135, and time information 143 related tothe current time associated with the client device 120 a. As previouslydiscussed, the time information 143 may be identified from the deviceprofile 123 of the client device 120 a or based at least in part on dataassociated with the network 110, such as an indication of the locationof the client device 120 a.

On a first request for access, the distribution service 174 maydetermine that the client device 120 a is authorized to access thedistribution server 150 as the user credentials 132 and deviceidentifier 135 associated with the client device 120 a are authorized.The distribution service 174 may further determine whether the clientdevice 120 a is authorized to access resources 165 based on the timerules 191 associated with the resources 165. The time information 143associated with the client device 120 a may indicate that the currenttime associated with the client device 120 a is 1 PM. Accordingly, thedistribution service 174 may authorize the client device 120 a to accessthe resources 165 because the current time of 1 PM falls within theauthorized window of 12:01 PM-1 PM specified by the time rules 191associated with the resources 165. For example, the distribution service174 may transmit the resources 165 to the client device 120 a to providethe client device 120 a with access to the resources 165.

While the client device 120 a may be authorized to access the resources165 upon receipt, the client device 120 a may cease to be authorizedbased on any changes in the current time associated with the clientdevice 120 a. To this end, the client side application 126 may monitorthe time information 143 associated with the client device 120 a todetermine whether the client device 120 a satisfies the time rules 191.If the client device 120 a fails to satisfy some or all of the timerules 191, then the client side application 126 may remove access to theresources 165 on the client device 120 a. For example, the client sideapplication 126 may permit the resources 165 to remain stored in aninaccessible format on client device 120 a because the client device 120a is located within the authorized location 1001.

In another embodiment, the client side application 126 executed byclient device 120 b may transmit a request 177 for access to resources165 to the distribution service 174 that may include user credentials132, a client device identifier 135, and time information 143 specifyingthe current time associated with the client device 120 b. As previouslydiscussed, the time information 143 may be identified from the deviceprofile 123 of the client device 120 b or based at least in part on dataassociated with the network 110. On a first request for access, thedistribution service 174 may determine that the client device 120 b isauthorized to access the distribution server 150 as the user credentials132 and device identifier 135 associated with the client device 120 bare authorized. The distribution service 174 may further determinewhether the client device 120 b is authorized to access resources 165based on the time rules 191 associated with the resources 165. The timeinformation 143 associated with the client device 120 b may indicatethat current time associated with the client device 120 b is 1 PM.Accordingly, the distribution service 174 may authorize the clientdevice 120 b to access the resources 165 because the current time of 1PM falls within the authorized window of 12:01 PM-1 PM specified by thetime rules 191 associated with the resources 165. For example, thedistribution service 174 may transmit the resources 165 to the clientdevice 120 b to provide the client device 120 b with access to theresources 165.

While the client device 120 b may be authorized to access the resources165 upon receipt, the client device 120 b may cease to be authorizedbased on any changes in the current time associated with the clientdevice 120 b. To this end, the client side application 126 may monitorthe time information 143 associated with the client device 120 b todetermine whether the client device 120 b satisfies the time rules 191.If the client device 120 b fails to satisfy some or all of the timerules 191, then the client side application 126 may remove access to theresources 165 on the client device 120 b. For example, the client sideapplication 126 may delete the resources 165 from the client device 120b because the client device 120 b is not located within the authorizedlocation 1001.

In a further embodiment, the client side application 126 executed byclient device 120 c may transmit a request 177 for access to resources165 to the distribution service 174 that may include user credentials132, a client device identifier 135, and time information 143 specifyingthe current time associated with the client device 120 c. As previouslydiscussed, the time information 143 may be identified from the deviceprofile 123 of the client device 120 c or based at least in part on dataassociated with the network 110. On a first request for access, thedistribution service 174 may determine that the client device 120 c isauthorized to access the distribution server 150 as the user credentials132 and device identifier 135 associated with the client device 120 care authorized. The distribution service 174 may further determinewhether the client device 120 c is authorized to access resources 165based on the time rules 191 associated with the resources 165. The timeinformation 143 associated with the client device 120 c may indicatethat current time associated with the client device 120 c is 12 PM.Accordingly, the distribution service 174 may not authorize the clientdevice 120 c to access the resources 165 because the current time of 12PM does not fall within the authorized window of 12:01 PM-1 PM specifiedby the time rules 191 associated with the resources 165.

The distribution service 174 may transmit a notice of non-compliance tothe client device 120 c that specifies that the client device 120 c isnot authorized to access the resources 165 at the current time of 12 PM.The distribution service 174 may further specify in the notice ofnon-compliance that the client device 120 c may become authorized toaccess the resources 165 at 12:01 PM. In response to receiving thenotice of non-compliance from the distribution service 174, the clientside application 126 may transmit another request 177 for access to theresources 165 at 12:01 PM. In particular, the client side application126 may transmit the request 177 once it has determined that the timeinformation 143 associated with the client device 120 c specifies thatthe current time associated with the client device 120 c is 12:01 PM. Inresponse to receiving such a request 177, the distribution service 174may authorize the client device 120 c to access the resources 165because the current time of 12:01 PM falls within the authorized windowof 12:01 PM-1 PM specified by the time rules 191 associated with theresources 165. For example, the distribution service 174 may transmitthe resources 165 to the client device 120 c to provide the clientdevice 120 c with access to the resources 165.

While the client device 120 c may be authorized to access the resources165 upon receipt, the client device 120 c may cease to be authorizedbased on any changes in the current time associated with the clientdevice 120 c. To this end, the client side application 126 may monitorthe time information 143 associated with the client device 120 c todetermine whether the client device 120 c satisfies the time rules 191.If the client device 120 c fails to satisfy some or all of the timerules 191, then the client side application 126 may remove access to theresources 165 on the client device 120 c. For example, the client sideapplication 126 may delete the resources 165 from the client device 120c because the client device 120 c is not located within the authorizedlocation 1001.

Finally, it is to be understood that the administrator of thedistribution service 174 may configure the resources 165 to beassociated with any combination of location rules 181, time rules 191,and distribution rules 171 to meet the varying security requirementsassociated with resources 165 that may be accessed over the network 110.The embodiments disclosed herein are only examples of the functionalityprovided by a distribution service 174 and a client side application 126for controlling access to resources 165 on a network 110, and may becombined and/or altered without departing from the scope and substanceof the disclosure.

FIG. 11 is a further example of a browsing interface 137 b, according tocertain embodiments of the present disclosure. The exemplary browsinginterface 137 b provides functionality for browsing resources 165(FIG. 1) accessible to the client device 120 (FIG. 1). In this example,the browsing interface 137 h includes a location-specific contentnavigation area 1103, presented in browsing interface 137 h as“Locations,” and a time-specific content navigation area 1106, presentedin browsing interface 137 h as “Times.”

The location-specific content navigation area 1103 may present resources165 accessible to the client device 120 based on the location of theclient device 120. In particular, the resources 165 are organizedaccording to a plurality of location rules 181 (FIG. 1) associated withthe resources 165 that specify where the client device 120 is authorizedto access the resources 165. If the location information 133 (FIG. 1)associated with the client device 120 indicates that the client device120 is located within an authorized location defined by a location rule181, the browsing interface 137 b may provide an indication that therespective grouping of resources 165 is accessible. For example, thebrowsing interface 137 b may indicate that a grouping of resources 165is accessible by not superimposing a restricted symbol over the iconassociated with the relevant grouping of resources 165. Conversely, ifthe location information 133 associated with the client device 120indicates that the client device 120 is not located within an authorizedlocation, the browsing interface 137 b may provide an indication thatthe respective grouping of resources 165 is not accessible. For example,the browsing interface 137 b may indicate that a grouping of resources165 is not accessible by superimposing a restricted symbol over the iconassociated with the relevant grouping of resources 165.

As an example, a client device 120 may be located within the “BoardRoom” and the Board Room may be located within the United States ofAmerica. The browsing interface 137 b may provide an indication of whichresources 165 are accessible by the client device 120 based on theclient device 120 being located within the Board Room. Thelocation-specific content navigation area 1103 may present fourgroupings of resources 165, such as the “All Locations” resourcegrouping 1103 a, the “U.S.A.” resource grouping 1103 b, the “Board Room”resource grouping 1103 c, and the “Europe” resource grouping 1103 d.

The “All Locations” resource grouping 1103 a may include all of theresources 165 that the client device 120 may be authorized to accessbased on the location of the client device 120. The client device 120 isauthorized to access resources 165 restricted to the U.S.A. based on itslocation within the U.S.A and resources 165 restricted to the Board Roombased on its location within the Board Room. Accordingly, the “AllLocations” resource grouping 1103 a may include the resources 165 fromthe “U.S.A.” resource grouping 1103 b and the “Board Room” resourcegrouping 1103 c. The browsing interface 137 b does not superimpose arestricted symbol over the icon associated with the “All Locations”resource grouping 1103 a to indicate that such resource grouping ispresently accessible by the client device 120. Similarly, as clientdevice 120 may be authorized to access the “U.S.A.” resource grouping1103 b and “Board Room” resource grouping 1103 c based on its location,the browsing interface 137 b does not superimpose a restricted symbolover the icon associated with either the “U.S.A.” resource grouping 1103b or “Board Room” resource grouping 1103 c to indicate that suchresource groupings are presently accessible by the client device 120. Onthe other hand, the client device 120 may not be authorized to accessthe “Europe” resource grouping 1103 d as the client device 120 is notlocated within Europe. Thus, the browsing interface 137 b maysuperimpose a restricted symbol over the icon associated with the“Europe” resource grouping 1103 d to indicate that such resourcegrouping is not presently accessible by the client device 120.

Similarly, the time-specific content navigation area 1106 may presentresources 165 accessible to the client device 120 based on the currenttime associated with the client device 120. In particular, the resources165 are organized according to a plurality of time rules 191 (FIG. 1)associated with the resources 165 that specify at what times the clientdevice 120 is authorized to access the resources 165. If the timeinformation 143 (FIG. 1) associated with the client device 120 indicatesthat the current time associated with the client device 120 is within anauthorized window defined by a time rule 191, the browsing interface 137b may provide an indication that the respective grouping of resources165 is accessible. Conversely, if the time information 143 associatedwith the client device 120 indicates that the current time associatedwith the client device 120 is not within an authorized window, thebrowsing interface 137 b may provide an indication that the respectivegrouping of resources 165 is not accessible.

Continuing with the example, the current time associated with the clientdevice 120 may be 13:00:01 on 7/23/2012. The browsing interface 137 bmay provide an indication of which resources 165 are accessible to theclient device 120 based on the current time associated with the clientdevice 120 of 13:00:01 on 7/23/2012. The time-specific contentnavigation area 1106 may present three groupings of resources 165, suchas the “All Times” resource grouping 1106 a, the “7/23/201213:00:00-7/23/2012 14:00:00” resource grouping 1106 b, and the“7/24/2012 09:00:00-7/24/2012 10:00:00” resource grouping 1106 c.

The “All Times” resource grouping 1106 a may include all of theresources 165 that the client device 120 may be authorized to accessbased on the current time associated with the client device 120. Theclient device 120 is authorized to access resources 165 restricted tothe authorized window between 7/23/2012 13:00:00 and 7/23/2012 14:00:00based on the current time of 7/23/2012 13:00:01. Accordingly, the “AllTimes” resource grouping 1106 a may include the resources 165 from the“7/23/2012 13:00:00-7/23/2012 14:00:00” resource grouping 1106 b. Thebrowsing interface 137 b does not superimpose a restricted symbol overthe icon associated with the “All Times” resource grouping 1106 a toindicate that such resource grouping is presently accessible by theclient device 120. Similarly, as client device 120 may be authorized toaccess the “7/23/2012 13:00:00-7/23/2012 14:00:00” resource grouping1106 b based on the current time, the browsing interface 137 b does notsuperimpose a restricted symbol over the icon associated with the“7/23/2012 13:00:00-7/23/2012 14:00:00” resource grouping 1106 b toindicate that such resource grouping is presently accessible by theclient device 120. On the other hand, the client device 120 may not beauthorized to access the “7/24/2012 09:00:00-7/24/2012 10:00:00”resource grouping 1106 c as the current time associated with the clientdevice 120 is not within the authorized window between 7/24/201213:00:00 and 7/24/2012 14:00:00 based on the current time of 13:00:01 on7/23/2012. Accordingly, the browsing interface 137 b may superimpose arestricted symbol over the icon associated with the “7/24/201209:00:00-7/24/2012 10:00:00” resource grouping 1106 c to indicate thatsuch resource grouping is not presently accessible by the client device120.

FIG. 12 is yet a further example of a browsing interface 137 b,according to certain embodiments of the present disclosure. Theexemplary browsing interface 137 b provides functionality for browsingresources 165 (FIG. 1) accessible to the client device 120 (FIG. 1). Inthis example, the browsing interface 137 b includes a compliance errormessage 1203 to alert the user that the client device 120 is no longerauthorized to access the resources 165 were being accessed, based on thecurrent state of the client device 120.

While preventing client devices 120 from initially gaining unauthorizedaccess to resources 165 may be sufficient to protect some resources 165,more sensitive resources 165 may require protection on a continuousbasis to ensure that the client device 120 remains compliant with anylocation rules 181 (FIG. 1) and/or time rules 191 (FIG. 1) associatedwith the resources 165. Responsive to a determination that a clientdevice 120 is no longer authorized to access resources 165 based onchanges to the location information 133 (FIG. 1) and/or time information143 (FIG. 1) associated with the client device 120, the client device120 may be required to initiate mediatory action in accordance with anyunsatisfied location rules 181 and/or time rules 191 associated with theresources 165. For example, the location rules 181 and/or time rules 191associated with the resources 165 may require the removal of theresources 165 from client devices 120 that are no longer compliant withthe associated location rules 181 and/or time rules 191.

Thus, the location rules 181 associated with the resources 165 belongingto the “Board Room” resource grouping 1103 c (FIG. 11) may be furtherconfigured to require that the associated resources 165 be removed fromthe client device 120 that is no longer located within the “Board Room.”Similarly, the time rules 191 associated with the resources 165belonging to the “7/23/2012 13:00:00-7/23/2012 14:00:00” resourcegrouping 1106 b (FIG. 11) may be further configured to require that theassociated resources 165 be removed from the client device 120 if thecurrent time associated with the client device 120 is no longer withinthe authorized time window from 7/23/2012 13:00:00 to 7/23/201214:00:00. Furthermore, in the event that the client device 120 fails tocomply with the location rules 181 and/or time rules 191, the browsinginterface 137 b may be configured to provide a compliance error thatspecifies why the previously accessible resources 165 may no longer beaccessed by the client device 120.

As exemplified in FIG. 11, the client device 120 was initiallyauthorized to access resources 165 belonging to the “Board Room”resource grouping 1103 c and resources 165 belonging to the “7/23/201213:00:00-7/23/2012 14:00:00” resource grouping 1106 b. The client device120 was authorized to access the “Board Room” resource grouping 1103 cas the location information 133 associated with the client device 120satisfied the location rules 181 associated with the “Board Room”resource grouping 1103 c. The client device 120 was further authorizedto access the “7/23/2012 13:00:00-7/23/2012 14:00:00” resource grouping1106 b as the time information 143 associated with the client device 120satisfied the time rules 191 associated with the “7/23/201213:00:00-7/23/2012 14:00:00” resource grouping 1106 b.

As an example, the client device 120 may no longer be presently locatedwithin the “Board Room” and the current time associated with the clientdevice 120 may no longer fall within the authorized window from7/23/2012 13:00:00 to 7/23/2012 14:00:00. Accordingly, the client device120 may no longer authorized to access either the resources 165belonging to the “Board Room” resource grouping 1103 c or the resources165 belonging to the “7/23/2012 13:00:00-7/23/2012 14:00:00” resourcegrouping 1106 b. The client device 120 may not be authorized to accessthe “Board Room” resource grouping 1103 c as the location information133 associated with the client device 120 does not satisfy the locationrules 181 associated with the “Board Room” resource grouping 1103 c.Similarly, the client device 120 may not be authorized to access the“7/23/2012 13:00:00-7/23/2012 14:00:00” resource grouping 1106 b as thetime information 143 associated with the client device 120 does notsatisfy the time rules 191 associated with the “7/23/201213:00:00-7/23/2012 14:00:00” resource grouping 1106 b.

Consequently, the client device 120 may initiate mediatory action inaccordance with the unsatisfied location rules 181 associated with the“Board Room” resource grouping 1103 c and the unsatisfied time rules 191associated with the “7/23/2012 13:00:00-7/23/2012 14:00:00” resourcegrouping 1106 b. In particular, the client device 120 may delete theresources 165 belonging to the “Board Room” resource grouping 1103 c andthe “7/23/2012 13:00:00-7/23/2012 14:00:00” resource grouping 1106 bfrom the client device 120. Additionally, the client device 120 mayprovide a compliance error message 1203 on the browsing interface 137 bto notify the user of the client device 120 of why the client device 120is no longer authorized to access the previously authorized resources165. The compliance error message 1203 may specify that the clientdevice 120 is incompliant for the previously authorized resources 165because the “Client Device is not located at ‘Board Room’” and the“Current Time is not between: 7/23/2012 13:00:00 and 7/23/201214:00:00.” The compliance error message 1203 may further specify thatthe “relevant resources have been deleted” from the client device 120and that the client device 120 “will be unable to access the relevantresources” until the client device 120 is compliant with the associatedlocation rules 181 and/or time rules 191. Finally, the browsinginterface 137 b may superimpose a restricted symbol over the iconsassociated with the “Board Room” resource grouping 1103 c and the“7/23/2012 13:00:00-7/23/2012 14:00:00” resource grouping 1106 b toindicate to that the client device 120 is not authorized to access theresources 165 belonging to such resource groupings.

FIG. 13 is a further example of a landing interface 137 e for anadministrator of the distribution service 174 (FIG. 1) executed by thedistribution server 150 (FIG. 1), according to certain embodiments ofthe present disclosure. The exemplary landing interface 137 e includes aresource group indicator 501, navigation area 503, and a documents area506. In one embodiment, the resource group indicator 501 may depict aresource grouping identifier 154 (FIG. 1) currently being managed. As anexample, the user interface 137 e depicts the resources 165 associatedwith the resource grouping identifier 154 (FIG. 1) called “BoardMeeting.” A drop-down button may be associated with the resource groupindicator 501 for managing resources 165 (FIG. 1) associated with otherresource grouping identifiers 154. The navigation area 503 may include aplurality of navigation controls that permit the user to manage theresources 165 hosted by the distribution server 150 that are associatedwith the resource grouping identifier 154 depicted by the resourceindicator 501. For example, the navigation controls may include aplurality of buttons, such as a “documents” button, to manage resources165 associated with the “Board Meeting” resource grouping identifier154.

Additionally, the documents area 506 includes a listing of resources 165that are associated with the resource grouping identifier 154 depictedby the resource indicator 501. In one embodiment, the resources 165 maybe presented in a table 509 where each row in the table includesidentifying information for each of the respective resources 165. Forinstance, the table may include a name of the resource 165, a type ofthe resource 165, a brief description of the resource 165, an authorizedlocation 1303 associated with the resource 165, an authorized start time1306 a of an authorized window associated with the resource 165, and anauthorized end time 1306 b of an authorized window associated with theresource 165.

The authorized location 1303 may represent one or more locations where aclient device 120 may be located to be authorized to access theresources 165, as specified by one or more location rules 181 (FIG. 1)associated with the resources 165. The authorized start time 1306 a mayrepresent one or more times when an authorized time window opens and theclient device 120 becomes authorized to access the resources 165, asspecified by one or more time rules 191 (FIG. 1) associated with theresources 165. The authorized end time 1306 b may represent one or moretimes when an authorized time window closes and the client device 120ceases to be authorized to access the resources 165, as specified by oneor more time rules 191. For example, the resources 165 associated withthe “Board Meeting” resource grouping identifier 154 may be accessed bya client device 120 located within the “Board Room” authorized location1303 between the authorized start time 1306 a of 7/23/2012 13:00:00 andthe authorized end time 1306 b of 7/23/2012 14:00:00.

In one embodiment, a plurality of management buttons 513 may also bepresented for each resource 165. For instance, the management buttons513 may permit the administrator to associate distribution rules 171(FIG. 1) with resources 165 uploaded to the distribution server 150,such as location rules 181 specifying a plurality of locations where theassociated resources 165 may be accessed and time rules 191 specifyingwhen the associated resources 165 may be accessed. The managementbuttons 513 may further permit the administrator to edit the resourcequalifiers 172 (FIG. 1) associated with the resource 165, add versioninformation, view a listing of resource grouping identifiers 154 withaccess to the respective resource 165, download a copy of the resource165, and remove the resource 165 from being hosted by the distributionserver 150. In another embodiment, the documents area 506 may alsoinclude an “add document” button 516, a “bulk import” button 519, andsorting options 523. For instance, invoking the “add document” button516 may call the distribution service 174 to add new resources 165 to behosted by the distribution server 150, as is described with respect toFIGS. 6 and 7. Additionally, invoking the “bulk import” button 519 maycall the distribution service 174 to simultaneously add and/or importmultiple resources 165, as can be appreciated. Further, the sortingoptions 523 may include a plurality of options for the administrator tosort the resources 165 presented in the table 509, such as according toa resource category, a resource type and/or any other sorting option.

FIG. 14 is a flowchart illustrating exemplary functionality performed bythe distribution service 174 (FIG. 1) according to certain embodiments.It is understood that the flowchart of FIG. 14 provides merely anexample of the many different types of functional arrangements that maybe employed to implement the operation of the distribution service 174as described herein. As an alternative, the flowchart of FIG. 14 may beviewed as depicting an example of steps of a method implemented in thedistribution server 150 (FIG. 1) according to one or more embodiments.While the flowchart of FIG. 14 illustrates exemplary functionalityperformed by the distribution service 174 with respect to a singleclient device 120, it is understood that the exemplary functionality ofthe distribution service 174 may be simultaneously performed withrespect to more than one client device 120.

Beginning with step 1403, the distribution service 174 receives arequest 177 (FIG. 1) from a client device 120 (FIG. 1) that requestsaccess to resources 165 (FIG. 1) hosted by the distribution server 150.In one embodiment, the request 177 may include a device identifier 135(FIG. 1) associated with a client device 120 and user credentials 132(FIG. 1) associated with the user operating the client device 120. Inanother embodiment, the request 177 may additionally include a deviceprofile 123 (FIG. 1) and/or may include specific elements of the deviceprofile 123 describing the state of a client device 120 such as locationinformation 133 (FIG. 1), time information 143 (FIG. 1), and/or anyother component of the device profile 123.

Next, in step 1406, the distribution service 174 determines whether theclient device 120 and the user operating the client device 120 areauthorized to access the distribution service 174. In one embodiment,the distribution service 174 may authorize the user and client device120 pairing according to the approach described in application Ser. No.13/316,073 entitled “CONTROLLING ACCESS TO RESOURCES ON A NETWORK,” asdescribed above. If the distribution service 174 determines that theuser may not access the distribution service 174 from the client device120, then the distribution service 174 may advance to step 1430 andnotify the user of the failed authorization. For instance, thedistribution service 174 may transmit a notification that specifies thatthe user is not authorized to access the distribution service 174 fromthe client device 120.

Returning to step 1406, if the distribution service 174 determines thatthe user may access the distribution service 174 from the client device120, then the distribution service 174 advances to step 1409. In step1409, the distribution service 174 identifies one or more resourcegrouping identifiers 154 that are associated with the client device 120.For example, the distribution service 174 may identify resource groupingidentifiers 154 associated with the client device 120 based on the usercredentials 132 and the device identifier 135. In one embodiment, aclient device 120 may be associated with one or more resource groupingidentifier 154, and a resource grouping identifier 154 may be associatedwith one or more client devices 120.

Next, in step 1412, the distribution service 174 identifies one or moreresources 165 that are associated with the determined resource groupingidentifiers 154. In one embodiment, a resource 165 may be associatedwith one or more resource grouping identifiers 154, and a resourcegrouping identifier 154 may be associated with one or more resources165. Then, in step 1415, the distribution service 174 identifies one ormore distribution rules 171 (FIG. 1) that are associated with theidentified resources 165. In particular, the distribution rules 171 mayinclude location rules 181 (FIG. 1) and/or time rules 191 (FIG. 1). Inone embodiment, a resource 165 may be associated with one or moredistribution rules 171. For example, the distribution rules 171 mayinclude location rules 181 and time rules 191, as discussed above. Uponidentifying all of the distribution rules 171 associated with theresources 165, the distribution service 174 proceeds to step 1418 anddetermines whether the identified distribution rules 171 include anylocation rules 181 and/or time rules 191.

If the distribution service 174 determines that the distribution rules171 include location rules 181, the distribution service 174 proceeds tostep 1421 to identify the location information 133 associated with theclient device 120. Similarly, if the distribution service 174 determinesthat the distribution rules 171 include time rules 191, the distributionservice 174 proceeds to step 1421 to identify the time information 143associated with the client device 120. In one embodiment, thedistribution service 174 may identify the location information 133and/or time information 143 from the device profile 123 associated withthe client device 120. In another embodiment, the distribution service174 may identify the location information 133 and/or time information143 based at least in part on network 110 (FIG. 10) data, globalpositioning data, a time server, and/or other approaches discussedabove. Returning to step 1418, if the distribution service 174determines that the distribution rules 171 neither include locationrules 181 nor time rules 171, then the distribution service 174 mayproceed to step 1424.

Next, in step 1424, the distribution service 174 determines whether theclient device 120 from which the request 177 was received complies withthe distribution rules 171 associated with each one of the identifiedresources 165, including any identified location rules 181 and/or timerules 191. In one embodiment, the distribution service 174 determineswhether the client device 120 is compliant based on the device profile123 associated with the client device 120. For instance, thedistribution service 174 may have received the device profile 123 inconjunction with the request 177. In another embodiment, thedistribution service 174 determines whether the client device 120 iscompliant with the distribution rules 171, such as the location rules181 and the time rules 191, based at least in part on locationinformation 133 and/or time information 143 identified and/or receivedby the distribution service 174.

If the distribution service 174 determines that the client device 120does not comply with any of the distribution rules 171 associated witheach one of the resources 165, then the distribution service 174proceeds to step 1430 and transmits a notification of noncompliance tothe client device 120. In one embodiment, the distribution service 174may determine that the client device 120 complies with the distributionrules 171 of a portion of the identified resources 165. For example, thedistribution service 174 may transmit a notification of noncompliance tothe client device 120 that specifies which of the identified resources165 the client device 120 is not authorized to access and specifieswhich distribution rules 171 associated with such resources 165 are notsatisfied by the client device 120.

Returning to step 1424, if the distribution service 174 determines thatthe client device 120 complies with the distribution rules 171 of alland/or a portion of the identified resources 165, the distributionservice 174 proceeds to step 1427 and transmits the authorized resources165 to the client device 120. In one embodiment, the distributionservice 174 may transmit the authorized resources 165 to a client sideapplication 126 (FIG. 1) on the client device 120. For example, theclient side application 126 may be containerized, thereby restrictingthe authorized resources 165 from being transmitted outside of thecontainerized environment of the client side application 126. Forexample, the containerized client side application 126 may prohibit theresources 165 from being cut, copied, pasted, and/or otherwise accessedoutside of the containerized environment of the client side application126.

In one embodiment, the distribution service 174 may transmit theauthorized resources 165 to the client device 120 based on itscompliance with the distribution rules 171 associated with suchresources 165. In another embodiment, the distribution service 174 maymake the authorized resources 165 available for download by the clientdevice 120. For instance, the client device 120 may receive anindication that the resource 165 is available for download and may, inresponse, transmit a request 177 to the distribution service 174 todownload the resource 165. Upon receiving the request 177, thedistribution service 165 may transmit the resource 165 to the clientdevice 120. In a further embodiment, the distribution rules 171associated with the resources 165 may be transmitted in conjunction withthe resources 165 to enable the client device 120 to continuouslymonitor its compliance with the distribution rules 171. For instance, aclient side application 126 on the client device 120 may be configuredto continuously or periodically determine whether the client device 120remains authorized to access the received resources 165.

FIG. 15 is a flowchart illustrating exemplary functionality performed bythe distribution service 174 (FIG. 1) according to certain embodiments.It is understood that the flowchart of FIG. 15 provides merely anexample of the many different types of functional arrangements that maybe employed to implement the operation of the distribution service 174as described herein. As an alternative, the flowchart of FIG. 15 may beviewed as depicting an example of steps of a method implemented in thedistribution server 150 (FIG. 1) according to one or more embodiments.While the flowchart of FIG. 15 illustrates exemplary functionalityperformed by the distribution service 174 with respect to a singleclient device 120, it is understood that the exemplary functionality ofthe distribution service 174 may be simultaneously performed withrespect to more than one client device 120.

Beginning with step 1503, the distribution service 174 identifies aclient device 120 with access to one or more resources 165 associatedwith the distribution service 174 that are accessible through acontainerized client side application 126 on the client devices 120.Resources 165 may be identified as accessible through a containerizedclient side application 126 if the resources 165 are associated withmetadata specifying that the resources 165 may only be accessed on theclient device 120 through a containerized client side application 126.Additionally, resources 165 may be identified as associated with thedistribution service 174 if one or more copies of the resources 165 arestored on the data store 153 of the distribution server 150. In oneembodiment, the distribution service 174 may call the client device 120to query its data store 122 to determine whether one or more resources165 stored on the data store 122 are associated with the distributionservice 174. In another embodiment, the distribution service 174 maytransmit a listing of resources 165 stored by the distribution service174 to the client device 120 and request a response specifying whetherone or more of the listed resources 165 reside on data store 122 of theclient device 120.

Next, in step 1506, the distribution service 174 identifies one or moredistribution rules 171 (FIG. 1) that are associated with the identifiedresources 165. In particular, the distribution rules 171 may includelocation rules 181 (FIG. 1) and/or time rules 191 (FIG. 1).Additionally, a resource 165 may be associated with one or moredistribution rules 171, and a distribution rule 171 may be associatedwith one or more resources 165. In one embodiment, the distributionservice 174 may determine whether the identified resources 165 areassociated with distribution rules 171 that are stored on the data store153 of the distribution server 150. In another embodiment, thedistribution service 174 may request to query the data store 122 of theclient device 120 to determine whether the contents of its data store122 contains distribution rules 171 associated with the identifiedresources 165. Upon identifying one or more distribution rules 171associated with the identified resources 165, the distribution service174 proceeds to step 1509 and determines whether the identifieddistribution rules 171 include any location rules 181 and/or time rules191.

If the distribution service 174 determines that the distribution rules171 include location rules 181, the distribution service 174 proceeds tostep 1512 to identify the location information 133 associated with theclient device 120. Similarly, if the distribution service 174 determinesthat the distribution rules 171 include time rules 191, the distributionservice 174 proceeds to step 1512 to identify the time information 143associated with the client device 120. In one embodiment, thedistribution service 174 may identify location information 133 and/ortime information 143 from the device profile 123 of the client device120. In another embodiment, the distribution service 174 may identifylocation information 133 and/or time information 143 based at least inpart on network 110 (FIG. 10) data, as previously described. However, ifthe distribution service 174 determines that the distribution rules 171neither include location rules 181 nor time rules 171, then thedistribution service 174 may proceed to step 1515.

Next, in step 1515, the distribution service 174 determines whether theclient device 120 complies with the distribution rules 171 associatedwith each one of the identified resources 165, including any identifiedlocation rules 181 and/or time rules 191. In one embodiment, thedistribution service 174 may determine whether the client device 120 iscompliant based on the device profile 123 of the client device 120. Forinstance, the distribution service 174 may call the client sideapplication 126 of the client device 120 to retrieve the device profile123 of the client device 120. In another embodiment, the distributionservice 174 may determine whether the client device 120 is compliantwith the distribution rules 171 based on location information 133 and/ortime information 143 identified by the distribution service 174.

If the distribution service 174 determines that the client device 120 iscompliant with the distribution rules 171 associated with the identifiedresources 165, then the distribution service 174 proceeds to step 1518and provides continued access to the resources 165 on the client device120. In one embodiment, the distribution service 174 may call the clientdevice 120 to instruct the client side application 126 to continue toprovide access to the resources 165. In another embodiment, thedistribution service 174 may take no action and rather allow the clientside application 126 of the client device 120 to continue to provideaccess to the resources 165 without instruction from the distributionservice 174.

Returning to step 1515, if the distribution service 174 determines thatthe client device 120 does not comply with the distribution rules 171such as the location rules 181 and the time rules 191, then thedistribution service 174 proceeds to step 1521 and removes theidentified resources 165 from the client device 120. In one embodiment,the distribution service 174 may remove the identified resources 165from the client device 120 by instructing the client device 120 todelete the identified resources 165 from the client device 120. Inanother embodiment, the distribution service 174 may remove theidentified resources 165 from the client device 120 by instructing theclient device 120 to configure the resources 165 to be inaccessibleand/or invisible to the client device 120. In yet another embodiment,the distribution service 174 may remove the identified resources 165from the client device 120 by instructing the client device 120 torestore the client device 120 its default state. In yet anotherembodiment, the distribution service 174 may remove the identifiedresources 165 from the client device 120 by instructing the clientdevice 120 to delete all data residing on the client device 120.

Additionally, in step 1524, the distribution service 174 transmits anotification of noncompliance to the client device 120. In oneembodiment, the distribution service 174 may transmit a notification ofnoncompliance to the client device 120 that specifies one or moreidentified resources 165 and specifies that such identified resources165 have been deleted from the client device 120 due to noncompliancewith the distribution rules 171 associated with the identified resources165. In another embodiment, in the event that location rules 181 and/ortime rules 191 associated with the identified resources 165 are notsatisfied by the client device 120, the distribution service 174 maytransmit a notification of noncompliance to the client device 120 thatfurther specifies the locations and times when the client device 120 mayaccess the identified resources 165 based on the location rules 181and/or time rules 191 associated with the resources 165.

While the distribution service 174 may determine that the client device120 currently complies and/or does not currently comply with thedistribution rules 171, the client device 120 may cease to comply and/orbegin to comply with the distribution rules 171 due to changes to thestate of the client device 120 over time. For instance, as the locationinformation 133 and/or time information 143 associated with the clientdevice 120 may change based on any changes to the location of the clientdevice 120 or the current time associated with the client device 120,the client device 120 may become or cease to be authorized for access toresources 165. Thus, to ensure the ongoing security of the resources165, the client side application 126 may continuously determine whetherthe client device 120 is authorized to access the resources 165 byreturning to step 1603 after either providing access to the resources165 in step 1621 or denying access to the resources 165 in steps 1624and 1627.

FIG. 16 is a flowchart illustrating exemplary functionality performed bya client side application 126 (FIG. 1) executed by a client device 120(FIG. 1) according to certain embodiments. It is understood that theflowchart of FIG. 16 provides merely an example of the many differenttypes of functional arrangements that may be employed to implement theoperation of the client side application 126 as described herein. As analternative, the flowchart of FIG. 16 may be viewed as depicting anexample of steps of a method implemented in the client device 120according to one or more embodiments.

Beginning with step 1603, the client side application 126 transmits arequest 177 (FIG. 1) to the distribution service 174 (FIG. 1) to accessresources 165 (FIG. 1). In one embodiment, the request 177 may includeuser credentials 132 (FIG. 1) associated with the user of the clientdevice 120 and a device identifier 135 (FIG. 1) associated with theclient device 120. For instance, the client side application 126 maypopulate the request 177 by prompting the user of the client device 120to provide user credentials 132 associated with the distribution service174 and may identify the device identifier 135 associated with theclient device 120 from the device profile 123 (FIG. 1) of the clientdevice 120. In another embodiment, the request 177 may include thedevice profile 123 (FIG. 1) associated with the client device 120, aspreviously described.

Next, in step 1606, the client device 120 receives a transmission of oneor more resources 165 from the distribution service 174. In oneembodiment, the client device 120 may receive each of the resources 165associated with the request 177 previously transmitted to thedistribution service 174. In another embodiment, the client device 120may only receive the resources 165 associated with the request 177 thatclient device 120 is authorized to access. For instance, the clientdevice 120 may receive resources 165 that distribution service 174 hasdetermined that the client device 120 is authorized to access based onelements of the request 177, such as user credentials 132 associatedwith the user of the client device 120 and a device identifier 135associated with the client device 120.

Additionally, in step 1609, the client side application 126 receives oneor more distribution rules 171 (FIG. 1) associated with the resources165 received from the distribution service 174. In particular, eachresource 165 may be associated with one or more distribution rules 171,and each distribution rule 171 may be associated with one or moreresources 165. For instance, a video resource 165 may be associated witha location rule 181 and a time rule 191 specific to a board meeting, andthe same location rule 181 may be associated the video resource 165, apicture resource 165 and a document resource 165.

Upon receiving the distribution rules 171, in step 1612, the client sideapplication 126 determines whether the distribution rules 171 receivedfrom the distribution service 174 include any location rules 181 and/ortime rules 191. If the client side application 126 determines that thedistribution rules 171 include location rules 181, then the client sideapplication 126 proceeds to step 1615 to identify the locationinformation 133 associated with the client device 120. Similarly, if theclient side application 126 determines that the distribution rules 171include time rules 191, then the client side application 126 proceeds tostep 1615 to identify the time information 143 associated with theclient device 120. In one embodiment, the client side application 126may identify the location information 133 and/or time information 143from the device profile 123 associated with the client device 120. Inanother embodiment, the client side application 126 may identify thelocation information 133 and/or time information 143 based at least inpart on network 110 (FIG. 10) data, as previously described. On thecontrary, if the client side application 126 determines that thedistribution rules 171 include neither location rules 181 nor time rules171, then the client side application 126 may proceed to step 1618without identifying the location information 133 and/or time information143 associated with the client device 120.

Next, in step 1618, the client side application 126 determines whetherthe client device 120 complies with the distribution rules 171associated with each one of the resources 165, including any identifiedlocation rules 181 and/or time rules 191. In one embodiment, the clientside application 126 may determine whether the client device 120 iscompliant based on the device profile 123 associated with the clientdevice 120. For example, the client side application 126 may determinewhether the client device 120 is compliant with the distribution rules171 based on location information 133 and/or time information 143 storedin the device profile 123 of the client device 120.

If the client side application 126 determines that the client device 120is compliant with the distribution rules 171 associated with theresources 165, then the client side application 126 proceeds to step1621 and provides the client device 120 with access to the resources165. On the contrary, if the client side application 126 determines thatthe client device 120 does not comply with the distribution rules 171associated with the resources 165, then the client side application 126proceeds to step 1624 and removes the resources 165 from the clientdevice 120. In one embodiment, the client side application 126 mayremove the resources 165 from the client device 120 by deleting theresources 165 from the client device 120. In another embodiment, theclient side application 126 may remove the resources 165 from the clientdevice 120 by configuring the resources 165 to be inaccessible and/orinvisible to the client device 120. In yet another embodiment, theclient side application 126 may remove the resources 165 from the clientdevice 120 by restoring the client device 120 to its default state. Inyet another embodiment, the client side application 126 removes theresources 165 from the client device 120 by removing all data from theclient device 120.

Additionally, in step 1627, the client side application 126 renders anotice of noncompliance on the client device 120. In one embodiment, theclient side application 126 may render a notification of noncompliancethat specifies the identities of the removed resources 165 and specifiesthat the resources 165 have been removed from the client device 120 dueto noncompliance with the distribution rules 171 associated with theresources 165. In another embodiment, the client side application 126may render a notification of noncompliance on the client device 120 thatfurther specifies the locations and times when the client device 120 mayaccess the identified resources 165 based on the location rules 181and/or time rules 191 associated with the resources 165.

While the client side application 126 may determine that the clientdevice 120 currently complies with the distribution rules 171 associatedwith the resources 165, the client device 120 may cease to comply withthe distribution rules 171 based on changes to the state of the clientdevice 120 over time. Similarly, while the client side application 126may determine that the client device 120 currently does not currentlycomply with the distribution rules 171 associated with the resources165, the client device 120 may begin to comply with the distributionrules 171 based on changes to the state of the client device 120 overtime. For instance, as the location information 133 associated with theclient device 120 may change over time based on changes to the locationof the client device 120, the client device 120 may either becomeauthorized for access to the resources 165 or may cease to be authorizedfor access to resources 165. Additionally, as the time information 143associated with the client device 120 may change overtime based onchanges to current time associated with the client device 120, theclient device 120 may either become authorized for access to theresources 165 or may cease to be authorized for access to resources 165.Thus, to ensure the ongoing security of the resources 165, the clientside application 126 may continuously determine whether the clientdevice 120 is authorized to access the resources 165 by returning tostep 1603 after either providing access to the resources 165 in step1621 or denying access to the resources 165 in steps 1624 and 1627.

FIG. 17 is a flowchart illustrating exemplary functionality performed bya client side application 126 (FIG. 1) according to certain embodiments.It is understood that the flowchart of FIG. 17 provides merely anexample of the many different types of functional arrangements that maybe employed to implement the operation of the client side application126 as described herein. As an alternative, the flowchart of FIG. 17 maybe viewed as depicting an example of steps of a method implemented inthe client device 120 (FIG. 1) according to one or more embodiments.

Beginning with step 1703, the client side application 126 identifies oneor more resources 165 associated with the distribution service 174(FIG. 1) that are accessible through a containerized client sideapplication 126 on the client device 120. Resources 165 may beidentified as accessible through a containerized client side application126 if the resources 165 are associated with metadata specifying thatthe resources 165 may only be accessed on the client device 120 througha containerized client side application 126. Additionally, resources 165may be identified as associated with the distribution service 174 if oneor more copies of the resources 165 are stored on the data store 153 ofthe distribution server 150. In one embodiment, the client sideapplication 126 may call the distribution service 174 to query the datastore 153 of the distribution server 150 to determine whether one ormore resources 165 stored on the data store 153 reside on the clientdevice 120. In another embodiment, the client side application 126 maytransmit a listing of resources 165 stored by the client device 120 tothe distribution service 174 and request a response specifying whetherone or more of the listed resources 165 reside on data store 153 of thedistribution server 150.

Next, in step 1706, the client side application 126 identifies thedistribution rules 171 (FIG. 1) that are associated with the identifiedresources 165. In particular, the distribution rules 171 may includelocation rules 181 (FIG. 1) and/or time rules 191 (FIG. 1).Additionally, a resource 165 may be associated with one or moredistribution rules 171, and a distribution rule 171 may be associatedwith one or more resources 165. In one embodiment, the client sideapplication 126 may determine whether distribution rules 171 associatedwith the identified resources 165 reside on the client device 120. Inanother embodiment, the client side application 126 may call thedistribution service 174 to query the data store 153 of the distributionserver 150 to determine whether the contents of its data store 153contain distribution rules 171 associated with the identified resources165. Upon identifying one or more distribution rules 171 associated withthe identified resources 165, the client side application 126 proceedsto step 1709 and determines whether the identified distribution rules171 include any location rules 181 and/or time rules 191.

If the client side application 126 determines that the distributionrules 171 include location rules 181, then the client side application126 proceeds to step 1712 to identify the location information 133associated with the client device 120. Similarly, if the client sideapplication 126 determines that the distribution rules 171 include timerules 191, then the client side application 126 proceeds to step 1615 toidentify the time information 143 associated with the client device 120.In one embodiment, the client side application 126 may identify thelocation information 133 and/or time information 143 from the deviceprofile 123 associated with the client device 120. In anotherembodiment, the client side application 126 may identify the locationinformation 133 and/or time information 143 based at least in part onnetwork 110 (FIG. 10) data, as previously described. On the contrary, ifthe client side application 126 determines that the distribution rules171 include neither location rules 181 nor time rules 171, then theclient side application 126 may proceed to step 1715 without identifyingthe location information 133 and/or time information 143 associated withthe client device 120.

Next, in step 1715, the client side application 126 determines whetherthe client device 120 complies with the distribution rules 171associated with each one of the resources 165, including any identifiedlocation rules 181 and/or time rules 191. In one embodiment, the clientside application 126 may determine whether the client device 120 iscompliant based on the device profile 123 associated with the clientdevice 120. In another embodiment, the client side application 126 maydetermine whether the client device 120 is compliant based on locationinformation 133 and/or time information 143 associated with the clientdevice 120 identified by the client side application 126.

If the client side application 126 determines that the client device 120is compliant with the distribution rules 171 associated with theresources 165, then the client side application 126 proceeds to step1621 and provides the client device 120 with access to the resources165. On the contrary, if the client side application 126 determines thatthe client device 120 does not comply with the distribution rules 171associated with the resources 165, then the client side application 126proceeds to step 1624 and removes the resources 165 from the clientdevice 120. In one embodiment, the client side application 126 mayremove the resources 165 from the client device 120 by deleting theresources 165 from the client device 120. In another embodiment, theclient side application 126 may remove the resources 165 from the clientdevice 120 by configuring the resources 165 to be inaccessible and/orinvisible to the client device 120. In yet another embodiment, theclient side application 126 may remove the resources 165 from the clientdevice 120 by restoring the client device 120 to its default state. Inyet another embodiment, the client side application 126 removes theresources 165 from the client device 120 by removing all data from theclient device 120.

Additionally, in step 1724, the client side application 126 renders anotice of noncompliance on the client device 120. In one embodiment, theclient side application 126 may render a notification of noncompliancethat specifies the identities of the removed resources 165 and specifiesthat the resources 165 have been removed from the client device 120 dueto noncompliance with the distribution rules 171 associated with theresources 165. In another embodiment, the client side application 126may render a notification of noncompliance on the client device 120 thatfurther specifies the locations and times when the client device 120 mayaccess the identified resources 165 based on the location rules 181and/or time rules 191 associated with the resources 165.

While the client side application 126 may determine that the clientdevice 120 currently complies with the distribution rules 171 associatedwith the resources 165, the client device 120 may cease to comply withthe distribution rules 171 based on changes to the state of the clientdevice 120 over time. Similarly, while the client side application 126may determine that the client device 120 currently does not currentlycomply with the distribution rules 171 associated with the resources165, the client device 120 may begin to comply with the distributionrules 171 based on changes to the state of the client device 120 overtime. For instance, as the location information 133 associated with theclient device 120 may change over time based on changes to the locationof the client device 120, the client device 120 may either becomeauthorized for access to the resources 165 or may cease to be authorizedfor access to resources 165. Additionally, as the time information 143associated with the client device 120 may change overtime based onchanges to current time associated with the client device 120, theclient device 120 may either become authorized for access to theresources 165 or may cease to be authorized for access to resources 165.Thus, to ensure the ongoing security of the resources 165, the clientside application 126 may continuously determine whether the clientdevice 120 is authorized to access the resources 165 by returning tostep 1703 after either providing continued access to the resources 165in step 1718 or denying access to the resources 165 in steps 1721 and1724.

FIG. 18 shows schematic block diagrams of an exemplary distributionserver 150 and an exemplary client device 120 according to an embodimentof the present disclosure. The distribution server 150 includes at leastone processor circuit, for example, having a processor 1803 and a memory1806, both of which are coupled to a local interface 1809. To this end,the distribution server 150 may comprise, for example, at least oneserver computer or like device. Similarly, the client device 120includes at least one processor circuit, for example, having a processor1853 and a memory 1856, both of which are coupled to a local interface1859. Additionally, the client device 120 may be in data communicationwith a display 136 for rendering user interfaces 137 (FIG. 1) and one ormore other I/O devices 1863 for inputting and outputting data. To thisend, the client device 120 may comprise, for example, at least oneclient computer or like device.

The following is a general discussion of the components of thedistribution server 150 and the client device 120. The local interface1809 and 1859 may comprise, for example, a data bus with an accompanyingaddress/control bus or other bus structure as can be appreciated. Storedin the memory 1806 and 1856 are both data and several components thatare executable by the processors 1803 and 1853. In particular, withregard to the distribution server 150, stored in the memory 1806 andexecutable by the processor 1803 are a distribution service 174 andpotentially other applications. Additionally, with regard to the clientdevice 120, stored in the memory 1856 and executable by the processor1853 are a client side application 126 and potentially otherapplications. Also stored in the memory 1806 and 1856 may be a datastore 153 and 122 and other data. In addition, an operating system maybe stored in the memory 1806 and 1856 and executable by the processor1803 and 1853.

It is to be understood that there may be other applications that arestored in the memory 1806 and 1856 and are executable by the processor1803 and 1853 as can be appreciated. Where any component discussedherein is implemented in the form of software, any one of a number ofprogramming languages may be employed such as, for example, C, C++, C#,Objective C, Java, JavaScript, Perl, PHP, Visual Basic, Python, Ruby,Delphi, Flash, or other programming languages.

A number of software components are stored in the memory 1806 and 1856and are executable by the processor 1803 and 1853. In this respect, theterm “executable” means a program file that is in a form that canultimately be run by the processor 1803 and 1853. Examples of executableprograms may be, for example, a compiled program that can be translatedinto machine code in a format that can be loaded into a random accessportion of the memory 1806 and 1856 and run by the processor 1803 and1853, source code that may be expressed in proper format such as objectcode that is capable of being loaded into a random access portion of thememory 1806 and 1856 and executed by the processor 1803 and 1853, orsource code that may be interpreted by another executable program togenerate instructions in a random access portion of the memory 1806 and1856 to be executed by the processor 1803 and 1853, etc. An executableprogram may be stored in any portion or component of the memory 1806 and1856 including, for example, random access memory (RAM), read-onlymemory (ROM), hard drive, solid-state drive, USB flash drive, memorycard, optical disc such as compact disc (CD) or digital versatile disc(DVD), floppy disk, magnetic tape, or other memory components.

The memory 1806 and 1856 are defined herein as including both volatileand nonvolatile memory and data storage components. Volatile componentsare those that do not retain data values upon loss of power. Nonvolatilecomponents are those that retain data upon a loss of power. Thus, thememory 1806 and 1856 may comprise, for example, random access memory(RAM), read-only memory (ROM), hard disk drives, solid-state drives, USBflash drives, memory cards accessed via a memory card reader, floppydisks accessed via an associated floppy disk drive, optical discsaccessed via an optical disc drive, magnetic tapes accessed via anappropriate tape drive, and/or other memory components, or a combinationof any two or more of these memory components. In addition, the RAM maycomprise, for example, static random access memory (SRAM), dynamicrandom access memory (DRAM), or magnetic random access memory (MRAM) andother such devices. The ROM may comprise, for example, a programmableread-only memory (PROM), an erasable programmable read-only memory(EPROM), an electrically erasable programmable read-only memory(EEPROM), or other like memory device.

Also, the processor 1803 and 1853 may represent multiple processors, andthe memory 1806 and 1856 may represent multiple memories that operate inparallel processing circuits, respectively. In such a case, the localinterface 1809 and 1859 may be an appropriate network 110 (FIG. 1) thatfacilitates communication between any two of the multiple processor 1803and 1853, or between any two of the memory 1806 and 1856, etc. The localinterface 1809 and 1859 may comprise additional systems designed tocoordinate this communication, including, for example, performing loadbalancing. The processor 1803 and 1853 may be of electrical or of someother available construction.

Although the distribution service 174, client side application 126, andother various systems described herein may be embodied in software orcode executed by general purpose hardware as discussed above, as analternative the same may also be embodied in dedicated hardware or acombination of software/general purpose hardware and dedicated hardware.If embodied in dedicated hardware, each can be implemented as a circuitor state machine that employs any one of or a combination of a number oftechnologies. These technologies may include, but are not limited to,discrete logic circuits having logic gates for implementing variouslogic functions upon an application of one or more data signals,application specific integrated circuits having appropriate logic gates,or other components, etc. Such technologies are generally well known bythose skilled in the art and, consequently, are not described in detailherein.

The flowcharts of FIGS. 8, 9, 14, 15, 16, and 17 show certainfunctionality and operations performed by the distribution service 174and client side application 126, respectively. If embodied in software,each box may represent a module, segment, or portion of code thatcomprises program instructions to implement the specified logicalfunction(s). The program instructions may be embodied in the form ofsource code that comprises human-readable statements written in aprogramming language or machine code that comprises numericalinstructions recognizable by a suitable execution system such as aprocessor 1803 and 1853 in a computer system or other system. Themachine code may be converted from the source code, etc. If embodied inhardware, each block may represent a circuit or a number ofinterconnected circuits to implement the specified logical function(s).

Although the flowcharts of FIGS. 8, 9, 14, 15, 16, and 17 show aspecific order of execution, it is understood that the order ofexecution may differ from that which is depicted. For example, the orderof execution of two or more steps may be scrambled relative to the ordershown. Also, two or more blocks shown in succession in FIGS. 8, 9, 14,15, 16, and 17 may be executed concurrently or with partial concurrence.Further, in some embodiments, one or more of the steps shown in FIGS. 8,9, 14, 15, 16, and 17 may be skipped or omitted. In addition, any numberof counters, state variables, warning semaphores, or messages might beadded to the logical flow described herein, for purposes of enhancedutility, accounting, performance measurement, or providingtroubleshooting aids, etc. It is understood that all such variations arewithin the scope of the present disclosure.

Also, any logic or application described herein, including thedistribution service 174 and the client side application 126, thatcomprises software or code can be embodied in any non-transitorycomputer-readable medium for use by or in connection with an instructionexecution system such as, for example, a processor 1803 and 1853 in acomputer system or other system. In this sense, the logic may comprise,for example, statements including instructions and declarations that canbe fetched from the computer-readable medium and executed by theinstruction execution system. In the context of the present disclosure,a “computer-readable medium” can be any medium that can contain, store,or maintain the logic or application described herein for use by or inconnection with the instruction execution system. The computer-readablemedium can comprise any one of many physical media such as, for example,magnetic, optical, or semiconductor media. More specific examples of asuitable computer-readable medium would include, but are not limited to,magnetic tapes, magnetic floppy diskettes, magnetic hard drives, memorycards, solid-state drives, USB flash drives, or optical discs. Also, thecomputer-readable medium may be a random access memory (RAM) including,for example, static random access memory (SRAM) and dynamic randomaccess memory (DRAM), or magnetic random access memory (MRAM). Inaddition, the computer-readable medium may be a read-only memory (ROM),a programmable read-only memory (PROM), an erasable programmableread-only memory (EPROM), an electrically erasable programmableread-only memory (EEPROM), or other type of memory device.

It should be emphasized that the above-described embodiments of thepresent disclosure are merely possible examples of implementations setforth for a clear understanding of the principles of the disclosure.Many variations and modifications may be made to the above-describedembodiment(s) without departing substantially from the spirit andprinciples of the disclosure. All such modifications and variations areintended to be included herein within the scope of this disclosure andprotected by the following claims.

Therefore, the following is claimed:
 1. A non-transitorycomputer-readable medium embodying a program executable in a computingdevice, the program comprising code that, when executed by a computingdevice, causes the computing device to perform a method comprising thesteps of: receiving, from a client device, a request to access aplurality of resources hosted by a distribution service; determiningwhether a pairing of a user of the client device and the client deviceis authorized to access the distribution service; identifying which of aplurality of resource grouping identifiers are associated with the userand client device pairing, in response to the determination that theuser and client device pairing is authorized to access the server;identifying which of a plurality of resources are associated with theresource grouping identifiers; identifying which of a plurality ofdistribution rules are associated with the identified resources, thedistribution rules comprising at least one of a plurality of locationrules or a plurality of time rules; and, transmitting the identifiedresources and the identified distribution rules to the client device,the resources being configured to be exclusively accessible via acontainerized client side application while the client device satisfiesthe distribution rules associated with the resources.
 2. Thecomputer-readable medium of claim 1, wherein the containerized clientside application is configured to enforce a plurality of transmissionrestrictions while the resources are being accessed by the containerizedclient side application, wherein the transmission restrictions compriseprohibiting transmitting, cutting, copying, and pasting the resources.3. The computer-readable medium of claim 1, wherein the containerizedclient side application is pre-installed on the client device.
 4. Thecomputer-readable medium of claim 1, wherein the location rules comprisea plurality of authorized locations where the resources may be accessedby the client device.
 5. The computer-readable medium of claim 4,wherein the authorized locations correspond to locations of meetings,and wherein the resources associated with the authorized locations arespecifically related to the meetings.
 6. The computer-readable medium ofclaim 1, wherein the time rules comprise a plurality of authorized timewindows during which the resources may be accessed by the client device.7. The computer-readable medium of claim 6, wherein the authorized timewindows correspond to time windows of meetings, and wherein theresources associated with the authorized time windows are specificallyrelated to the meetings.
 8. The computer-readable medium of claim 1,further comprising the step of: removing the resources from the clientdevice if the client device does not satisfy the distribution rulesassociated with the resources.
 9. The computer-readable medium of claim8, wherein removing the resources from the client device comprises atleast one of deleting the resources from the client device, disablingthe resources on the client device, restoring the client device to itsdefault state, and deleting all data from the client device.
 10. Thecomputer-readable medium of claim 1, wherein the distribution rulesfurther comprise at least one of a plurality of client device hardwarerequirements, a plurality of client device software requirements, aplurality of client device configuration requirements, a plurality ofclient device maintenance requirements, and a plurality of resourcerelated requirements.
 11. The computer-readable medium of claim 1,wherein the user and client device pairing is authorized to access thedistribution service based at least in part on a plurality of usercredentials associated with the user and a device identifier associatedwith the client device, and wherein the request comprises usercredentials and a device identifier.
 12. A method comprising:determining, via a containerized client side application being executedby a client device, whether the client device is located at one of aplurality of authorized locations; responsive to a determination thatthe client device is located at an authorized location, transmitting arequest for access to a plurality of resources to a distributionservice; receiving resources that are configured to be exclusivelyaccessible via the containerized client side application; and, removingthe resources from the client device if the client device is no longerlocated at an authorized location.
 13. The method of claim 12, whereinthe containerized client side application is configured to enforce aplurality of transmission restrictions while the resources are beingaccessed by the containerized client side application, wherein thetransmission restrictions comprise prohibiting transmitting, cutting,copying, and pasting the resources.
 14. The method of claim 12, whereinthe containerized client application is pre-installed on the clientdevice.
 15. The method of claim 12, wherein the authorized locations arebound at least in part by one or more of a plurality of physicalboundaries, a plurality of virtual boundaries, and a plurality ofeconomic boundaries.
 16. The method of claim 12, wherein the authorizedlocations correspond to locations of meetings, and wherein the resourcesassociated with the authorized locations are specifically related to themeetings.
 17. The method of claim 12, wherein removing the resourcesfrom the client device comprises at least one of deleting the resourcesfrom the client device, disabling the resources on the client device,restoring the client device to its default state, and deleting all datafrom the client device.
 18. The method of claim 12, further comprising:determining whether the current time is within of a plurality ofauthorized time windows before transmitting the request to access theresources; and, removing the requested resources from the client deviceif the current time is not within an authorized time window, whereinremoving the resources from the client device comprises at least one ofdeleting the resources from the client device, disabling the resourceson the client device, restoring the client device to its default state,and deleting all data from the client device.
 19. The method of claim12, wherein the authorized time windows correspond to time windows ofmeetings, and wherein the resources associated with the authorized timewindows are specifically related to the meetings.
 20. The method ofclaim 12, further comprising: determining whether a pairing of a user ofthe client device and the client device is authorized to access thedistribution service before transmitting the request to accessresources, wherein the client device is authorized to access thedistribution service based at least in part on a plurality of usercredentials associated with the user of the client device and a deviceidentifier associated with the client device; and, removing theresources from the client device if the user and client device pairingdoes is not authorized to access the distribution service, whereinremoving the resources from the client device comprises at least one ofdeleting the resources from the client device, disabling the resourceson the client device, restoring the client device to its default state,and deleting all data from the client device.
 21. The method of claim12, further comprising: determining whether the client device satisfiesa plurality of distribution rules associated with the resources beforetransmitting the request to access resources, wherein the distributionrules comprise at least one of a plurality of client device hardwarerequirements, a plurality of client device software requirements, aplurality of client device configuration requirements, a plurality ofclient device maintenance requirements, and a plurality of resourcerelated requirements; and, removing the resources from the client deviceif the client device does not satisfy the distribution rules, whereinremoving the resources from the client device comprises at least one ofdeleting the resources from the client device, disabling the resourceson the client device, restoring the client device to its default state,and deleting all data from the client device.
 22. A system fordistributing resources comprising: a processor; a memory deviceincluding instructions that when executed by the processor cause theprocessor to perform a method comprising the steps of: receiving, from aclient device, a request to access a plurality of resources hosted by adistribution service; determining whether a current time associated withthe client device is within one of a plurality of authorized timewindows associated with the resources; responsive to a determinationthat current time is within at least one of the authorized time windows,transmitting the resources to the client device; monitoring the currenttime; and removing the resources from the client device if the currenttime is not within an authorized time window.
 23. The system of claim22, wherein the authorized time windows correspond to time windows ofmeetings, and wherein the resources associated with the authorized timewindows are specifically related to the meetings.
 24. The system ofclaim 22, further comprising the steps of: configuring the resources tobe exclusively accessible via a containerized client application on theclient device before transmitting the resources to the client device.25. The system of claim 24, wherein the containerized client sideapplication is configured to enforce a plurality of transmissionrestrictions while the resources are being accessed by the containerizedclient side application, wherein the transmission restrictions compriseprohibiting transmitting, cutting, copying, and pasting the resources.26. The system of claim 22, wherein removing the resources from theclient device comprises at least one of deleting the resources from theclient device, disabling the resources on the client device, restoringthe client device to its default state, and deleting all data from theclient device.
 27. The system of claim 22, further comprising the stepsof: determining whether the client device is located at one of pluralityof authorized locations before transmitting the resources to the clientdevice; and, removing the resources from the client device if the clientdevice is not located at an authorized location, wherein removing theresources from the client device comprises at least one of deleting theresources from the client device, disabling the resources on the clientdevice, restoring the client device to its default state, and deletingall data from the client device.
 28. The system of claim 27, wherein theauthorized locations are bound at least in part by one or more of aplurality of physical boundaries, a plurality of virtual boundaries, anda plurality of economic boundaries.
 29. The system of claim 27, whereinthe authorized locations correspond to locations of meetings, andwherein the resources associated with the authorized locations arespecifically related to the meetings.
 30. The system of claim 22,further comprising the steps of: determining whether a pairing of a userof the client device and the client device is authorized to access thedistribution service before transmitting the resources to the clientdevice, wherein the client device is authorized to access thedistribution service based at least in part on a plurality of usercredentials associated with the user of the client device and a deviceidentifier associated with the client device; and, removing theresources from the client device if the user and client device pairingis not authorized to access the distribution service, wherein removingthe resources from the client device comprises at least one of deletingthe resources from the client device, disabling the resources on theclient device, restoring the client device to its default state, anddeleting all data from the client device.
 31. The system of claim 22,further comprising the steps of: determining whether the client devicesatisfies a plurality of distribution rules associated with theresources before transmitting the resources to the client device,wherein the distribution rules comprise at least one of a plurality ofclient device hardware requirements, a plurality of client devicesoftware requirements, a plurality of client device configurationrequirements, a plurality of client device maintenance requirements, anda plurality of resource related requirements; and, removing theresources from the client device if the client device does not satisfythe distribution rules, wherein removing the resources from the clientdevice comprises at least one of deleting the resources from the clientdevice, disabling the resources on the client device, restoring theclient device to its default state, and deleting all data from theclient device.
 32. A method comprising: receiving, from a client device,a request to access a plurality of resources hosted by a distributionservice; determining whether the client device is located at one of aplurality of authorized locations associated with the resources;responsive to a determination that the client device is located at anauthorized location, transmitting the resources to the client device;monitoring the location of the client device; and, removing theresources from the client device if the client device is not located atan authorized location.
 33. The method of claim 32, further comprising:configuring the resources to be exclusively accessible via acontainerized client side application on the client device beforetransmitting the resources to the client device, wherein thecontainerized client side application is pre-installed on the clientdevice and is configured to enforce a plurality of transmissionrestrictions while the resources are being accessed by the containerizedclient side application, wherein the transmission restrictions compriseprohibiting transmitting, cutting, copying, and pasting the resources.34. The method of claim 32, wherein the authorized locations are boundat least in part by one or more of a plurality of physical boundaries, aplurality of virtual boundaries, and a plurality of economic boundaries.35. The method of claim 32, wherein the authorized locations correspondto locations of meetings, and wherein the resources associated with theauthorized locations are specifically related to the meetings.
 36. Themethod of claim 32, wherein removing the resources from the clientdevice comprises at least one of deleting the resources from the clientdevice, disabling the resources on the client device, restoring theclient device to its default state, and deleting all data from theclient device.
 37. The method of claim 32, further comprising:determining whether the current time is within one of a plurality ofauthorized time windows before transmitting the resources to the clientdevice.
 38. The method of claim 37, wherein the authorized time windowscorrespond to time windows of meetings, and wherein the resourcesassociated with the authorized time windows are specifically related tothe meetings.
 39. The method of claim 32, further comprising: removingthe resources from the client device if the current time is not withinone of a plurality of authorized time windows, wherein removing theresources from the client device comprises at least one of deleting theresources from the client device, disabling the resources on the clientdevice, restoring the client device to its default state, and deletingall data from the client device.
 40. The method of claim 32, furthercomprising: determining whether a pairing of a user of the client deviceand the client device is authorized to access the distribution servicebefore transmitting the resources to the client device, wherein theclient device is authorized to access the distribution service based atleast in part on a plurality of user credentials associated with theuser of the client device and a device identifier associated with theclient device; and, removing the resources from the client device if theuser and client device pairing is not authorized to access thedistribution service, wherein removing the resources from the clientdevice comprises at least one of deleting the resources from the clientdevice, disabling the resources on the client device, restoring theclient device to its default state, and deleting all data from theclient device.
 41. The method of claim 32, further comprising:determining whether the client device satisfies a plurality ofdistribution rules associated with the resources before transmitting theresources to the client device, wherein the distribution rules compriseat least one of a plurality of client device hardware requirements, aplurality of client device software requirements, a plurality of clientdevice configuration requirements, a plurality of client devicemaintenance requirements, and a plurality of resource relatedrequirements; and, removing the requested resources from the clientdevice if the client device does not satisfy the distribution rules,wherein removing the resources from the client device comprises at leastone of deleting the resources from the client device, disabling theresources on the client device, restoring the client device to itsdefault state, and deleting all data from the client device.
 42. Anon-transitory computer-readable medium embodying a program executablein a computing device, the program comprising code that, when executedby a computing device, causes the computing device to perform a methodcomprising the steps of: transmitting, from a containerized client sideapplication executed by a client device, a request to access a pluralityof resources hosted by a distribution service; and, receiving access tothe resources via the containerized client side application if theclient device is located at one of a plurality of authorized locationsand if the current time is within one of a plurality of authorized timewindows.
 43. The computer-readable medium of claim 42, furthercomprising the steps of: configuring the resources to be exclusivelyaccessible on the client device via the containerized clientapplication.
 44. The computer-readable medium of claim 42, furthercomprising the steps of: monitoring the location of the client deviceand the current time.
 45. The computer-readable medium of claim 42,further comprising the steps of: removing access to the resources on theclient device if the client device is not located at an authorizedlocation; and, removing access to the resources on the client device ifthe current time is not within an authorized time window.
 46. Thecomputer-readable medium of claim 45, wherein removing access to theresources on the client device comprises at least one of deleting theresources from the client device, disabling the resources on the clientdevice, restoring the client device to its default state, and deletingall data from the client device.
 47. The computer-readable medium ofclaim 42, further comprising the steps of: removing access to theresources on the client device if a pairing of a user of the clientdevice and the client device is not authorized to access a distributionservice associated with the resources, wherein the user and clientdevice pairing is authorized to access the distribution service based atleast in part on a plurality of user credentials associated with theuser of the client device and a device identifier associated with theclient device; and, wherein removing access to the resources on theclient device comprises at least one of deleting the resources from theclient device, disabling the resources on the client device, restoringthe client device to its default state, and deleting all data from theclient device.
 48. The computer-readable medium of claim 42, furthercomprising the steps of: removing access to the resources on the clientdevice if the client device does not satisfy a plurality of distributionrules associated with the resources, wherein the distribution rulescomprise at least one of a plurality of client device hardwarerequirements, a plurality of client device software requirements, aplurality of client device configuration requirements, a plurality ofclient device maintenance requirements, and a plurality of resourcerelated requirements, and wherein removing access to the resources onthe client device comprises at least one of deleting the resources fromthe client device, disabling the resources on the client device,restoring the client device to its default state, and deleting all datafrom the client device.
 49. The computer-readable medium of claim 42,wherein the containerized client side application is configured toenforce a plurality of transmission restrictions while the resources arebeing accessed by the containerized client side application, wherein thetransmission restrictions comprise prohibiting transmitting, cutting,copying, and pasting the resources.
 50. The computer-readable medium ofclaim 42, wherein the containerized client application is pre-installedon the client device.
 51. The computer-readable medium of claim 42,wherein the authorized locations are bound at least in part by one ormore of a plurality of physical boundaries, a plurality of virtualboundaries, and a plurality of economic boundaries.
 52. Thecomputer-readable medium of claim 42, wherein the authorized locationscorrespond to locations of meetings, and wherein the resourcesassociated with the authorized locations are specifically related to themeetings.
 53. The computer-readable medium of claim 42, wherein theauthorized time windows correspond to time windows of meetings, andwherein the resources associated with the authorized time windows arespecifically related to the meetings.
 54. A client device operating in asystem for distributing resources, the client device comprising: aprocessor; a memory device including instructions that when executed bythe processor cause the processor to perform a method comprising thesteps of: determining whether a client device has access to a pluralityof resources associated with a plurality of authorized time windows;determining whether a current time associated with the client device iswithin an authorized time window; and removing access to the resourceson the client device if the current time is not within an authorizedtime window.
 55. The system of claim 54, wherein determining whether thecurrent time is within an authorized time window comprises determiningthe current time based at least in part on the location of the clientdevice.
 56. The system of claim 54, wherein removing access to theresources on the client device comprises at least one of deleting theresources from the client device, disabling the resources on the clientdevice, restoring the client device to its default state, and deletingall data from the client device.
 57. The system of claim 54, furthercomprising the steps of: determining whether the client device hasaccess to a plurality of resources associated with a plurality ofauthorized locations; determining whether the client device is locatedat an authorized location; and, remove access to the resources on theclient device if the client device is not located at an authorizedlocation, wherein removing access to the resources on the client devicecomprises at least one of deleting the resources from the client device,disabling the resources on the client device, restoring the clientdevice to its default state, and deleting all data from the clientdevice.
 58. The system of claim 56, wherein the authorized locationscorrespond to locations of meetings, and wherein the resourcesassociated with the authorized locations are specifically related to themeetings.
 59. The system of claim 54, further comprising the steps of:determining whether the client device has access to a plurality ofresources hosted by a distribution service, wherein the client device isauthorized to access the distribution service based at least in part ona plurality of user credentials associated with the user of the clientdevice and a device identifier associated with the client device; and,determining whether a pairing of a user of the client device and theclient device is authorized to access the distribution service; and,removing access to the resources on the client device if the user andclient device pairing is not authorized to access the distributionservice, wherein removing access to the resources on the client devicecomprises at least one of deleting the resources from the client device,disabling the resources on the client device, restoring the clientdevice to its default state, and deleting all data from the clientdevice.
 60. The system of claim 54, further comprising the steps of:determining whether the client device has access to a plurality ofresources associated with a plurality of distribution rules, wherein thedistribution rules comprise at least one of a plurality of client devicehardware requirements, a plurality of client device softwarerequirements, a plurality of client device configuration requirements, aplurality of client device maintenance requirements, and a plurality ofresource related requirements, and determining whether the client devicesatisfies the distribution rules; and, remove access to the resources onthe client device if the client device does not satisfy the distributionrules, wherein removing access to the resources on the client devicecomprises at least one of deleting the resources from the client device,disabling the resources on the client device, restoring the clientdevice to its default state, and deleting all data from the clientdevice.